Enterprise architecture analysis framework database

ABSTRACT

A method of modeling an enterprise includes storing core objects, where the core objects include an information object defining information used in the enterprise, a participant object defining a participant in the enterprise, an enabler object defining a tool used in the enterprise, and an activity object defining a process performed in the enterprise, and storing relationship objects that define interactions between two or more of the core objects.

TECHNICAL FIELD

This patent application relates generally to modeling an enterprise and, more particularly, to modeling the enterprise by defining elements in the enterprise, and interactions between those elements, as objects in a database.

BACKGROUND

The term “architecture” has been used to refer to various types of overviews that provide guidance to software systems and applications developers. Since the mid-1990s, the term “architecture” has been used by business managers, especially those involved in enterprise planning and in business process re-engineering projects, to describe an overview of a business. For example, some managers refer to a high-level description of all core business processes in an organization as a “business process architecture”.

Today, there is a growing movement among both business managers and information technology (“IT”) managers to use the term “enterprise architecture” to refer to a comprehensive description of all key elements and relationships that make up an organization. Increasingly, when professionals talk about the alignment of business processes and goals with IT applications and middleware systems, they rely on an enterprise architecture to define how this business/IT alignment should be achieved.

SUMMARY

In general, in one aspect, the invention is directed to a method of modeling an enterprise. The method includes storing core objects, where the core objects comprise an information object defining information used in the enterprise, a participant object defining a participant in the enterprise, an enabler object defining a tool used in the enterprise, and an activity object defining a process performed in the enterprise, and storing relationship objects that define interactions between two or more of the core objects. This aspect may also include one or more of the following features.

The method may include storing a cell comprising at least some of the core objects and the relationship objects, where the cell comprises a set of objects needed to complete a specific objective and/or derive the information; storing a process scenario object that links the cell with other cells, where the process scenario object defines how the information is transformed over time; and/or defining influences and settings that have a bearing on the process scenario. The process scenario object may be built in accordance with the influences and settings, and may include data defining a domain to which the process scenario object belongs. The domain may be a decision-making layer within the enterprise.

A single information object may be common to the process scenario object and a second process scenario object. The activity object and the information object may correspond to associated values. The method may determine a value of the process scenario based the associated values. The relationship objects may define one of common object relationships and cross-object relationships.

In general, in another aspect, the invention is directed to a method of modeling an enterprise, which includes building core objects that define elements of an enterprise, building relationship objects that define interactions between two or more of the core objects, building a cell comprising at least some of the core objects and the relationship objects, and relating the cell to other cells. This aspect may also include the following.

The core objects may comprise an information object defining information used in the enterprise, a participant object defining a participant in the enterprise, an enabler object defining a tool used in the enterprise, and an activity object defining a process performed in the enterprise. The cell and the other cells may define a process scenario, and the method may further comprise determining a value of the process scenario based on a value of the activity object and a value of the information object. The value of the process scenario may comprise a ratio of the value of the activity object to the value of the information object.

Other features and advantages described herein will be apparent from the description, the drawings, and the claims.

DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagram that depicts core objects conceptually.

FIG. 2 is a diagram that depicts common object relationships conceptually.

FIG. 3 a is a diagram that depicts common object relationships across decision control domains; and FIG. 3 b is a diagram that depicts common object relationships in a single decision control domain.

FIG. 4 is a diagram that depicts cross-object relationships conceptually.

FIG. 5 is a diagram that depicts a cell conceptually.

FIG. 6 is a diagram that depicts a process scenario conceptually.

FIG. 7 is a diagram that shows process scenarios for different decision control domains of an enterprise.

FIG. 8 depicts stacking of different decision control domains.

Like reference numerals in different figures indicate like elements.

DETAILED DESCRIPTION

The Enterprise Architecture Analysis Framework (“EAAF”) database defines logical linkages between enterprise business, information, solutions, and technical architectures. The EAAF database includes a collection of object-oriented relational tables, which can be used to develop and analyze an enterprise architecture's current, target and migration landscapes for consistency, capability and coverage; capture, define and harmonize the enterprise's IT infrastructure components and attributes; synchronize business goals, strategies, objectives, and performance criteria with IT capabilities and resources; and harmonize timeframes required by business operations with IT program initiatives schedules. The EAAF database takes an information-centric approach, rather than a process-centric approach, as described below

Core objects of the EAAF database include objects that define information (I), participants (P), activities (A) and enablers (E) of an enterprise. The core objects are described in detail below. Tables for the core objects constitute the fundamental building blocks of the EAAF database, and can be considered the “DNA” of the enterprise.

Relationships can be defined for the core objects. Relationship objects define how two or more core objects relate. There are two types of relationship objects: common object relationships and cross-object relationships. Common object relationships define relationships between identical or common core objects within the EAAF database, and include information to information (I2I), participant to participant (P2P), enabler to enabler (E2E), and activity to activity (A2A). Cross-object relationships define relationships between different core objects within the EAAF database, and include participant to information (P2I), participant to enabler (P2E), participant to activity (P2A), enabler to information (E2I), enabler to activity (E2A), and activity to information (A2I).

Core objects and relationship objects may be combined to model relationships and/or processes that occur in an enterprise. In this regard, a cell is an object that defines a set of interdependent relationships that describe an overall set of elements needed to complete a specific objective. A cell includes core objects and relationship objects that define relationships, in the cell, between the core objects. A process scenario is an object that defines relationships that cells have to one another in an overall process.

The EAAF database also contains value objects. Value objects specify objectives, benefits, metrics, influences, settings, domains and dimensions within the EAAF database. The value objects are related to cells in a process scenario, and can be used to define how different process scenarios generate value to the enterprise. The value objects also aid in constructing process scenarios by defining environmental settings that specify a landscape in which the process scenario is constructed and influences that impact the process scenario.

By assembling core objects, relationship objects, cells and process scenarios, the EAAF database is able to model an enterprise. The resulting objects can represent a single layer of the EAAF database, which encompass a domain of authority a participant controls (referred to herein as a “decision control domain”) and the span of information a participant uses to make a decision or to act. Several such domains may be “stacked”, e.g., interrelated, to model different aspects of the enterprise. Stacking provides an integrated view of the enterprise's participants, information, and processes for dynamic modeling.

Core Objects

In this embodiment, four core objects are stored in the EAAF database. These core objects are depicted conceptually in FIG. 1. As noted, these core objects include information (I) object 10, participant (P) object 11, enabler (E) object 12, and activity (A) object 14. Other embodiments may employ different types and/or numbers of core objects. The EAAF database defines a table for each of instance of a core object. Each such table contains user-customizable input and selection fields. These fields define, among other things, the subject matter and capabilities of each core object.

Information Object: What it is

The information object specifies information that describes an enterprise deliverable. An enterprise deliverable may be a physical object, such as a product or material, or an intangible object, such as a contract or an agreement. Data for the information object, or any other object described herein, may be input using a tool, e.g., software, a form, film, a disk, etc., and may be compiled from data coming from one or more sources, such as history, gauges, reports, visual inspection, thought, etc.

Any type of data may be included in an information object. For example, the information object may contain data that describes a category of the information (e.g., global, regional, local, functional, process), a type of the information (e.g., static, dynamic, analytic, unstructured), a state of the information (e.g., if it is still “good” data), a time value associated with the information (e.g., when the data was acquired), an update time frame for the information (e.g., how often the data's state changes), a quantity or volume of information, and a medium that stores the information (e.g., physical, electronic, optical).

Table 1 shows an exemplary definition of an information object. Other embodiments may employ different types of tables with different fields.

In Table 1, the field names identify variables that are included in the information object. The field types corresponds to groupings of fields that relate to the same concept. For example, “ID”, “Name”, and “Description” all serve to define the information object. “Req.” indicates whether the corresponding variable is mandatory (M) or optional (O). “Use” specifies how the corresponding variable is used in the information object. “Object Check” corresponds to the type of relationship object in which the variable may be employed. The type corresponds to the data type of the variable, e.g., Boolean, character, numeric, etc. “Ref.” indicates whether the corresponding variable can assume one or more different values. The reference table values constitute values that the variable can assume.

It is noted that the column definitions set forth above also apply to the remaining tables described herein.

TABLE 1 Object Reference Field Name Field Type Req. Description Use Check Type Ref. Table Values ID General M A non-intelligent Used to uniquely Auto N value that defines identify the number the unique “key” object as a for the database record and for record relating it with other objects Name M A non-intelligent Used to provide Character, N standard value the primary Field that describes the means of entry, object identifying and Length = 30 searching Description M An intelligent, Used to provide Character, N non-standard a secondary Field value that means of entry, describes the identify and Length = 255 object with searching greater detail Category Classification M The classification Used to Radio Y Static or value that defines determine the button dynamic the object's nature change aspect of the object Type M The classification Used to A2I Character, Y Statutory, value that determine the Selection, Regulatory, describes the business Length = 10 Trade, object's reason for requirement for Business, existence the information Public, etc. object Function M The classification Used to A2I Character, Y Financial, value that represent Selection, Qualitative, describes the process Length = 12 Quantitative, object's purpose scenarios for the Spatial, and function different flows Measurement, of information Descriptive, based on their etc. state and time sequence parameters State Control M The control value Used to define A2I; Character, Y Periodic, change that describes the periodicity I2I; Selection, Constant, interval when the of state changes E2I Length = 12 Irregular, (Update information i.e., how often it Sporadic, time frame) object's state will changes, over Cyclical, be changed time with Singular, respect to the Intermittent, interval time etc. scale State M The control value Used to define A2I; Character, Y Seconds, change that describes the the scale to the I2I; Selection, Minutes, interval time scale of update time E2I Length = 8 Hours, Days, scale when the state frame and the Week, etc. (Update change will occur periodicity of time scale) the update State M The control value Used to define A2I; Character, Y Event change that describes the the change E2I Selection, triggered, control mechanism that mechanism for Length = 12 Participant controls the the information triggered, information state and how it Time object's state is controlled triggered, change activity triggered, etc Persistence Usage M The usage value Used to E2I Numeric, N that describes how determine the Field long the storage time entry, information object required for an Length = 5 is required to exist information or is of value object Persistence O The usage value Used in E2I Character, Y Seconds, scale that defines the combination Selection, minutes, hours, scale of how long with the Length = 8 days, weeks, the information persistence field month, years, object is used to determine the etc. storage time Volume O The usage value Used to E2I Numeric, N that describes determined the length = 5 quantitatively the volume of use use of the object using a quantitative measurement Volume O The usage value Used in E2I Character, Y Each, pounds, scale that defines the combination Selection, kilograms, scale of the with the volume Length = 8 pages, bytes, volume field hours, etc. Storage Handling O The handling Used to E2I Character, Y Document, type value that determine the Selection, electronic, classifies the type of storage Length = 10 photographic, object's storage required for the imaging, etc requirement information object Storage O The handling Used to E2I Character, Y Paper, audio medium value that determined the Selection, tape, video describes the storage format Length = 10 tape, storage medium required for the microfiche, that the information velum, information object object for magnetic tape, will utilize validating the magnetic disk, E2I relationship optic disk, etc. Storage O The handling Used to E2I Character, Y Structured, mode value that determine the Selection, unstructured, describes the schema that is Length = 12 compiled, means by which required based graphical, the object is to be on the nature of other stored based on its the object to nature store it Sensitive Security M The security field Used to E2I Boolean N Yes/no that indicates determine if the whether the enabler has the information is of a proper security sensitive nature protocols to secure the information Legal M The security field Used to E2I Boolean N Yes/no requirement that indicates determine if the whether the enabler has the information must proper security be secured by law protocols to or regulation secure the information Security M The security field Used to E2I; A2I Character, Y Physical, protocol that describes the determine if the Selection, Electronic; security protocol enabler and the Length = 12 Both- that is required by activity has the Electronic & law or regulation proper security Physical protocols to secure the information Participant Object: Who does it

A participant is an entity that performs an activity. The activity may, or may not, be automated with a tool, such as an application or a machine embedded with programmable logic. The participant object represents the individual (or individuals) who performs the activity. The individual can be internal to the enterprise, e.g., an employee, or external to the enterprise, e.g., a customer, a consultant, or a supplier's employee.

Any type of data may be included in the participant object. For example, the participant object may contain data that describes a category of the participant (e.g., employee, customer, partner, supplier), a type of the participant (e.g., manager, technician, engineer), a function of the participant (e.g., engineering, accounting, marketing), an organizational entity that the participant belongs to, a location or “geography” of the participant (e.g., North America, Europe, Asia), the participant's mobility (e.g., fixed, local mobility, regional mobility), hardware and/or devices that the participant uses, and languages (e.g., English, French, German, Spanish) that the participant speaks/understands.

Table 2 shows an exemplary definition of a participant object. Other embodiments may employ a different type of table with different fields.

TABLE 2 Object Reference Table Field Name Field Type Req. Description Use Check Type Ref. Values ID General M A non-intelligent Used to Auto N value that defines uniquely number the unique “key” identify the for the database object as a record record and for relating it with other objects Name M A non-intelligent Used to provide Character, N standard value the primary Field that describes the means of entry, object identifying and Length = 30 searching Description M An intelligent, Used to provide Character, N non-standard a secondary Field value that means of entry, describes the identify and Length = 255 object with searching greater detail Category Classification M The classification Used to P2P Character, Y Owner, field that defines a determine how a Selection, Channel, participant's participant will Length = 15 Partner, nature and how perform, engage Worker, they will interact and operate Supplier, within an within an Manager, enterprise system enterprise Customer, system Neighbor, Other Function M The classification Used to P2P Character, Y Line function, field that defines a determine how a Selection, Staff function, participant's participant Length = 20 Matrix function, function within functions in a Mini the enterprise organization organization Role M The classification Used to P2P Character, Y Specialist, field that defines a determine how a Selection, Manager, participant's role participant Length = 20 Advocate, within the interacts with Adversary, etc enterprise other participants Legal Domain M The domain field Used to define P2I Character, Y Predefined entity defines the legal the legal span of Selection, reference table entity to which a access, control, Length = 15 values participant is authorization, assigned etc Organizational O The domain field Used to define P2I Character, Y Predefined entity defines the the Selection, reference table organizational organizational Length = 15 values entity to which a span of access, participant is control, assigned authorization, etc Mobility/ M The domain field Used to define P2I Character, Y Fixed, local, Dispersion that defines a how a Selection, regional, global, participant's participant's Length = 15 etc. mobility with responsibility is respect to maintained responsibility Geography/ Control O The control field Used to P2I Character, Y Predefined Region that defines the determine the Selection, reference table geographic scope geographic span Length = 15 values of responsibility of control for a for the participant participant Job class M The control field Used to Character, Y Predefined that defines the determine the Selection, reference table participant's job level of control Length = 20 values category a participant will be permitted to have Quantity O The control field Used to Numeric, N that defines the determine the Length = 5 total number of number of individual participants of a participants of this single class type Country Environment M The environment Used to P2A Character, Y Predefined field that defines a determine how Selection, reference table participant's culture will Length = 20 values location impact a participant State/ M The environment Used to P2A Character, Y Predefined Province/ field that defines a determine how Selection, reference table Territory participant's geography will Length = 20 values location impact a participant Facility M The environment Used to P2A Character, Y Predefined field that defines a determine a Selection, reference table participant's participant's Length = 20 values location information accessibility Language M The environment Used to P2I Indicator Y Predefined field that defines a determine how box reference table participant's language will (multiple values language and impact a selections dialect participant's permitted) enabler needs Education M The environment Used to P2I Indicator Y Predefined level field that defines a determine how a box reference table participant's participant's (multiple values knowledge and ability to selections skill level execute an permitted) activity or operate an enabler Input Accessibility O The accessibility Used to P2E Indicator Y Terminal, device field that determine how a box computer, PDA, describes the participant (multiple scanner, reader, input device used accesses selections phone, radio, etc by a participant enablers to permitted) execute their activities Connection O The accessibility Used to P2E Indicator Y CAT5, ADSL, medium field that determine how a box DSL, T1, ISDN, describes the participant may (multiple wireless, connection connect to selections WCDMA, etc. medium that a manage and permitted) participant uses to access access information information Output O The accessibility Used to P2E Indicator Y Fax, printer, device field that determine how a box CRT, phone, describes the participant will (multiple LCD, plotter, output device retrieve selections projector, etc. used by a information to permitted) participant in manage their performing their activities activities Security Security M The security field Used to validate P2I; Boolean N Yes, No required that indicates the information P2A whether a security and participant has a activity security security clearance protocols Activity Object: What is Done

An activity includes automated and/or manual tasks that generate a change in state of an object resulting in generation of information, or that generate a change in state of existing information. The activity object represents such tasks. The activity object may also represent a transformation of information via an activity. Such transformations may include, for example, transfer of information from a physical medium to electronic medium.

Any type of data may be included in the activity object. For example, the activity object may contain data that describes the category of the activity (e.g., manual, semi-automated, fully automated), the type of the activity (e.g., global, regional, local, other), the function of the activity (e.g., customer, industry, compliance, incidental), and whether and/or how the activity is controlled (e.g., regulated, un-regulated, mandated).

Table 3 shows an exemplary definition of an activity object. Other embodiments may employ a different type of table with different fields.

TABLE 3 Object Reference Table Field Name Field Type Req. Description Use Check Type Ref. Values ID General M A non-intelligent Used to uniquely Auto N value that defines identify the object number the unique “key” for as a record and the database record for relating it with other objects Name M A non-intelligent Used to provide Character, N standard value that the primary Field entry, describes the object means of Length = 30 identifying and searching Description M An intelligent, non- Used to provide a Character, N standard value that secondary means Field entry, describes the object of identify and Length = 255 with greater detail searching Category Classification M The classification Used to define the A21 Character, Y Manual, semi- field that defines level of Selection, automated, fully the nature of the automation and Length = 20 automated, activity with the flexibility within other, etc. system the activity's tasks Type M The classification Used to identify A2I Character, Y Regulated, non- field that describes the activity's Selection, regulated, whether there is controlling and Length = 20 legislated, control on the information mandated, etc. activity requirements Function M The classification Used to define the A2I Character, Y Production, field that describes primary driver or Selection, safety, the activity's reason for the Length = 20 compliance, purpose with activity and tasks quality, service, respect to the cost control, etc output Domain M The classification Used to the level A2I Character, Y Global, field that describes of standardization Selection, regional, the activity's span of the activity Length = 20 national, state, within the within the local, other, etc. enterprise system enterprise Policy Control O The control field Used to assist in P2A; Boolean N Yes, No Exists that identifies the impact A2I whether a policy assessment of an exist that describe organization's and or controls the policy and activity procedures for changes to activity Policy Name O The control field Used to assist in P2A; Character, Y e.g. Worker that identifies the the impact A2I Selection, Protection policy that assessment of an Length = 20 Standard describes and or organization's HR109 controls the activity policy and procedures for changes to activity Documented Compliance O The compliance Used to assist in P2A; Boolean N Yes, No Procedure field that identifies the impact A2I Exists whether a assessment of an procedure is organization's document for the policy and activity procedures for changes to activity Documented Compliance O The compliance Used to assist in P2A; Character, Y Worker safety, Procedure field that identifies the impact A2I Selection, Production Type the type of assessment of the Length = 20 process, Product procedure that change to an safety, Financial documents the activity on compliance, activity for compliance to a Maint. process, participants to regulation etc. follow Documented O The compliance Used to assist in P2A; Character, Y e.g. High Noise Procedure field that identifies the impact A2I Selection, Level the procedure that assessment of an Length = 20 Precaution, documents the organization's Equipment activity policy and clearance, procedures for Vendor changes to contracting, activity Procurement, etc Governmental M The compliance Used to assist in P2A; Boolean N Yes, No Regulation field that identifies the impact A2I Exists whether a assessment of the governmental change to a regulation exists activity on which controls the compliance to a activity regulation Governmental M The compliance Used to assist in P2A; Character, Y OSHA, DEP, Regulation field that identifies the impact A2I Selection, EPA, HUD, Type the type of assessment of the Length = 20 NIH, DOT, governmental change to a SEC, NRC, regulation that activity on OMB, etc. exists to control the compliance to a activity regulation Governmental M The compliance Used to assist in P2A; Character, Y e.g. US Product Regulation field that identifies the impact A2I Selection, Safety Act Name the governmental assessment of the Length = 20 1977, regulation that change to a exists to control the activity on activity compliance to a regulation Enabler Object: how it is Done

A tool is a manual task, or a set of programs installed as a whole and running on a single server, that performs a single business function. The enabler object reflects operational steps performed by the tool in the transformation of a deliverable through a series of actions. The operational steps result in information and a deliverable at a state that is usable to others (e.g., for use by another activity).

Any type of data may be included in the enabler object. For example, the enabler object may contain data that describes the purpose of the enabler (e.g., technical, operation management, financial, analysis, development, archiving, storage), a lifecycle date of the enabler (e.g., availability or out-of-maintenance), a data center location associated with the enabler, implementation information (e.g., project name, time frame, effort), and information about hardware associated with the enabler. This hardware information may include performance-per-user information (e.g., maximum processor, memory, bandwidth, and/or disk space per user), performance-per-document information (e.g., maximum processor, memory, bandwidth, and/or disk space per document), cluster server name, load balancer server name, security information, and language information (e.g., double-byte capability, multiple language capability). By way of example, an enabler can range from an embedded or programmable logic chip with machine language controlling a production machine that automates a production process to a software application that automates information flow and activities within a business or support process.

Table 4 shows an exemplary definition of an enabler object. Other embodiments may employ a different type of table with different fields.

TABLE 4 Object Reference Field Name Field Type Req. Description Use Check Type Ref. Table Values ID General M A non-intelligent Used to uniquely Auto N value that defines identify the number the unique “key” for object as a the database record record and for relating it with other objects Name M A non-intelligent Used to provide Character, N standard value that the primary Field describes the means of entry, object identifying and Length = 30 searching Description M An intelligent, Used to provide Character, N non-standard value a secondary Field that describes the means of entry, object with detail identify and Length = 255 searching Category Classification M The classification Used to define E2A Character, Y Manual, semi- field that describes the fundamental Selection, automated, the enabler itself, characteristic of Length = 20 automated, as to whether it the enabler as it other can operate performs an independently of a activity for a participant participant Class O The classification Used to define E2A Character, Y Customizable field that describes the flexibility of Selection, off-the-shelf, the development the enabler with Length = 35 custom environment used respect to its develop appl., to create and ability to embedded maintain the transform and logic chip, pre- enabler change over time programmed, etc. Type M The classification Used to define E2A Character, Y Control, field that defines the nature of the Selection, storage, the nature of enabler within Length = 25 measurement, activities that the the enterprise management, enable will system as it production, perform and operates to communication automate within automate and testing, the enterprise perform research, system activities tracking, etc. Function M The classification Used to identify E2I Character, Y Product design, field that describes the reason an Selection, maintenance, the business enabler is used Length = 25 payroll, billing, purpose or by a participant accounting, functions the reporting, etc. enabler supports Environment Domain M The domain field Used to define P2E Character, Y Field, factory, that describes the the setting that Selection, laboratory, setting that defines corresponds to Length = 20 office, how the enabler the usage of the classroom, supports an enabler within home, activity or allows a the enterprise transitory, participant to system warehouse, perform an aquatic, etc. activity Location Domain M The domain field Used to locate P2E; Character, Y Predefined that defines the the enabler in E2A Selection, reference table physical location relationship to a Length = 30 values of the enabler participant/ activity Ownership M The domain field Used to identify P2E Character, Y Predefined that defines the a participant's Selection, reference table legal ownership of rights with Length = 30 values the enabler respect to the enabler Encryption Security M The security field Used to E2I Boolean N Yes, No capability that defines the determine the ability of the enabler's ability enabler to secure to secure the information information Encryption O The security field Used to E2I Character, Y SNC, HTTPS, protocol that defines the set determined the Selection, etc. of rules that the protocol used by Length = 30 enabler uses to the enabler to secure the secure information information SSO O The security field Used to P2E Boolean N Yes, No capability that determines the determine the enabler's ability to enabler's ability support a single to enable a single sign-on logon for a environment participant UNICODE Environment O The environment Used to P2E Boolean N Yes, No capability field that defines determine the the enabler's enabler's ability capability to to support support multiple multiple language types participant language types Double O The environment Used to P2E Boolean N Yes, No byte field that identifies determine the character the capability of enabler's ability capability the enabler to to support a support specific participant's language types specific language type Architecture Infrastructure M The name of the Used to E2E; Character, Y Presentation, Tier architecture logical tier upon determine how P2E Selection, Application, which the an enabler's Length = 20 Database, enabler's application Middleware, application would be used Mainframe, operates in by a participant Desktop, etc. productive mode or how another enabler would integrate Server M Name of the server Used to E2E; Character, Y Predefined name on which the determine which P2E Selection, reference table enabler's enabler is Length = 20 application unavailable if a operates in server shutdowns productive mode System ID M Name of the Used to identify E2E; Character, Y Predefined application system the system name E2A Selection, reference table ID on which the for enabler Length = 5 enabler's integration application scenarios and operates in that will support productive mode the activity automation Clustered M The infrastructure Used to P2E; Boolean N Yes, No for High architecture field determine the E2A Availability that identifies the cluster server fail-over capability with automated of the enabler's script restart the application enabler's infrastructure for application in activity support case of server crash Cluster O Name of the Used to E2E; Character, Y Predefined server cluster server in determine which P2E Selection, reference table name which the server will be Length = 20 enabler's available to application operate the operates in fail- enabler's over mode application Load Infrastructure O The infrastructure Used to P2E; Boolean N Yes, No balanced architecture architecture field determine the E2A that identifies the load-balancing load balance server with capability of the automated script enabler's shift work load application for the enabler's infrastructure for application in activity support case of heavy load Load O Name of the load Used to E2E; Character, Y Predefined balancer balance server in determine which P2E Selection, reference table server which the server will be Length = 20 name enabler's available to application operate the operates in fail- enabler's over mode application Software Logical M Name of the Used to identify Character, Y Predefined name Architecture application that and distinguish Selection, reference table enabler operates the application Length = 15 values Software M Name of the Used to identify E2E; Character, Y Predefined name application version and distinguish E2A Selection, reference table release that the enabler the application Length = 10 values uses to operate in release for productive mode determining enabler integration and activity automation support Software O Name of the latest Used to E2A Character, Y Predefined correction/ application determine the Selection, reference table patch level correction patch enabler support Length = 5 values level active within level for the enabler assessing capability to support an activity Programming O Name of the Used to E2E; Character, Y Cobol, ABAP, language program language determine the P2E Selection, FORTRAN, used to create the capability to Length = 10 PLC, Java, C, enabler's logic support enabler C++, C#, MS- modules for event to enabler VB, etc. modeling and integration processing scenarios and enabler support OS M Name of the Used to E2E; Character, Y SUN, HP-UX, dependency operating system determine the E2A Selection, AIX, NT, the enabler will enablers Length = 10 W2000, WXP, function on in platform AS400, productive mode required to Mainframe, operate, integrate IBMZ-OS, with other Linux, etc. enablers and support activity automation OS M Name of the Used to E2E; Character, Y Predefined correction/ operating system determine the E2A Selection, reference table patch level patch level that the enabler support Length = 5 values enabler operates level required to on in productive operate, integrate mode with other enablers and support activity automation DB M Name of the Used to E2E, Character, Y Oracle, dependency database determine the E2A Selection, SAPDB, DB2- application the enablers Length = 10 400, DB2-390, enabler will platform DB2-UDB, function on in required to MS-SQL, productive mode operate, integrate Informix, etc. with other enablers and support activity automation DB patch M Name of the Used to E2E; Character, Y Predefined level database determine the E2A Selection, reference table application patch enabler support Length = 5 values level that the level required to enabler operates operate, integrate on in productive with other mode enablers and support activity automation Development Lifecycle M Current status of Used to E2A Character, Y In status the enabler's determine the Selection, development, application that status of the Length = 30 Beta version, operates/ enabler's Restricted automates the application for shipment, enterprise's the support of Mass activities the enterprise's shipment, activity Extended Maintenance, Customer Maintenance, Retired, etc. Availability O The date the Used to check E2A Date, Y Julian date enabler's functionality in a Field Calendar; application is version and entry, Format = YYYY/ available from the windows of Length = 10 MM/DD provider for opportunity for installation on the implementation enterprise hardware Installed M The date the Used to E2E; Date, Y Julian date enabler's determine the E2A Field Calendar; application was first date of entry, Format = YYYY/ install on the availability for Length = 10 MM/DD enterprise's an application hardware within the enterprise Last M The date the Used to E2E; Date, Y Julian upgrade enabler's determine the E2A Field Calendar; date application was date of the last entry, Format = YYYY/ upgrade on the version was Length = 10 MM/DD enterprise's installed for an hardware application Out of M The date the Used to E2E; Date, Y Julian maintenance application determine the E2A Field Calendar; date provider sets for date the entry, Format = YYYY/ the standard application will Length = 10 MM/DD maintenance no longer be agreement to supported expire Max Performance O This field defines Used to P2E Numeric, N Format = 99999 Participants the CPU's determine the Field per 1 CPU maximum number SLA with entry, of participants the participant Length = 5 enabler's requirements for application sizing the supports enabler's hardware Max users O This field defines Used to P2E Numeric, N Format = 99999 per 1 GB of the memory determine the Field memory setting's maximum SLA with entry, number of participant for Length = 5 participants sizing the supported enabler's hardware Max users O This field defines Used to P2E Numeric, N Format = 99999 per 1 GB of the disk's determine the Field disk space maximum number SLA with entry, of participants participant for Length = 5 supported sizing the enabler's hardware Max O This field defines Used to E2I Numeric, N Format = 99999 documents the CPU's determine the Field per 1 CPU maximum number SLA with entry, of documents documents for Length = 5 supported sizing the enabler's hardware Max O This field defines Used to E2I Numeric, N Format = 99999 documents the memory determine the Field per 1 GB of setting's maximum SLA with entry, memory number of documents for Length = 5 documents sizing the supported enabler's hardware Max O This field defines Used to E2I Numeric, N Format = 99999 documents the disk's determine the Field per 1 GB of maximum number SLA with entry, disk space of participants the documents for Length = 5 enabler's sizing the application enabler's supports hardware

Common Object Relationships

As described above, the EAAF database defines common-object relationships. The EAAF stores common-object relationship objects to represent such relationships between the core objects. The common object relationships are represented conceptually in FIG. 2. In this embodiment, the common object relationships include information to information (I2I) object 15, participant to participant (P2P) object 16, enabler to enabler (E2E) object 17, and activity to activity (A2A) object 19. Other embodiments may employ different types and numbers of common object relationship objects.

The EAAF database has a defined table for each of instance of a common object relationship object. Each such table contains user-customizable input and selection fields. These fields define the subject matter and capabilities of each object.

Information to Information Object: how Information is Structured

The information to information object defines relationships between information objects with data that is relevant within and/or across an EAAF domain. Any type of data may be included in the information to information object. For example, the information to information object may contain data that describes a category of the object (e.g., structure, unstructured), a type of the object (e.g., hierarchical, clustered, accumulated), a relationship of one information object to another information object (e.g., peer, subordinate, non-related), dependencies between information objects (e.g., time dependent, dependent, not dependent), and time value fields (e.g., an object's creation date and expiration date).

It is noted that, in Table 5 (and other tables), the “foreign key” refers to a parameter from another object. For example, “INFNM” corresponds to a code identifying one of the objects for which a relationship is being defined by the table.

Table 5 shows an exemplary definition of an information to information object. Other embodiments may employ a different type of table with different fields.

TABLE 5 Field Object Reference Field Name Type Req Description Use Check Type Ref. Table Values ID General M A non- Used to Auto N intelligent uniquely number value that identify the defines the object as a unique “key” record and for for the relating it with database record other objects Name M A non- Used to provide Character, N intelligent the primary Field standard value means of entry, that describes identifying and Length = 30 the object searching Description M An intelligent, Used to provide Character, N non-standard a secondary Field value that means of entry, describes the identify and Length = 255 object with searching detail Category Classification M The field that Used to identify Character, Y Peer-to-peer, categorizes the relationship Selection, Superior- the object within the Length = 30 Subordinate, relationship decision control etc domain structure Class M The field that Used to Character, Y Hierarchical, identifies the categorize the Selection, Clustered, object relationship Length = 30 Accumulated, relationship structure as to Singular, etc. structure the relationship of the information objects Type M The field that Used to define Character, Y Structure, identifies the how the Selection, Integration, type of the relationship is Length = 30 Collaboration, information used by the Communication, object objects for the Control, etc relationship performance of an activity Dependency Relationship M The field that Used to Character, Y Time- describes the determine the Selection, dependent, relationship of dependency of Length = 30 Activity- the the object dependent, information relationships Decision- objects dependent, etc. Info Object 1 M The field that Used to link the INFID Numeric, Y ID value from ID contains the two information (foreign Selection, Information first objects and key) Length = 7 Object Table information describe the object relationship identification key Info Object 1 M The field that Used to link the INFNM Character, Y Name value Name contains the two information (foreign Default, from first objects and key) Length = 30 Information information describe the Table Auto- object name relationship selected based value on INFID Info Object 2 M The field that Used to link the INFID Numeric, Y ID value from ID contains the two information (foreign Selection, Information second objects and key) Length = 7 Table information describe the object relationship identification key Info Object 2 Relationship M The field that Used to link the INFNM Character, Y Name value Name contains the two information (foreign Default, from second objects and key) Length = 30 Information information describe the Table Auto- object name relationship selected based value on INFID Lifecycle Lifecycle M The field that Used to check E2I Date, Y Julian start date identifies the relationship Field Calendar; when the of the enabler to entry, Format = YYYY/ relationship information Length = 10 MM/DD between the two objects began Lifecycle end M The field that Used to check E2I Date, Y Julian date identifies the relationship Field Calendar; when the of the enabler to entry, Format = YYYY/ relationship information Length = 10 MM/DD between the two objects end Participant to Participant Object: how Participants Relate to Each Other

The participant to participant object describes enterprise organization in terms of participant relationships using data that is relevant within and/or across an EAAF domain. This type of object references participant objects with data that shows how the participants identified by those participant objects relate to one another.

Any type of data may be included in the participant to participant object. For example, the participant to participant object may contain data that describes a category of the object (e.g., legal, regulatory, investment, commerce, educational, employment), a type of the object (e.g., knowledge development, collaboration, service delivery, communication, production), a relationship between participants indicated in the object (e.g., network, colleague, superior, customer), controls associated with the object (e.g., inspect, regulate, manage, influence), and time value fields.

Table 6 shows an exemplary definition of a participant to participant object. Other embodiments may employ a different type of table with different fields.

TABLE 6 Field Object Reference Table Name Field Type Req Description Use Check Type Ref. Values ID General M A non-intelligent Used to Auto N value that defines uniquely number the unique “key” identify the for the database object as a record record and for relating it with other objects Name M A non-intelligent Used to provide Character, N standard value the primary Field that describes the means of entry, object identifying and Length = 30 searching Description M An intelligent, Used to provide Character, N non-standard a secondary Field value that means of entry, describes the identify and Length = 255 object with detail searching Category Classification M The field that Used to Character, Y Legal, categorizes the identify the Selection, Regulatory, relationship relationship Length = 30 Investment, between the within the Commerce, participants decision Educational, control domain Employment, structure etc Type M The field that Used to P2E Character, Y Knowledge identifies the determine how Selection, Development, specific type of a relationship Length = 20 Collaboration, relationship may be Service between the impacted by Delivery, participants changes in an Communication, enabler Production, etc Engagement Relationship M The field that Used to P2A Character, Y Colleague, describes the determine how Selection, Superior, relationship of the a relationship Length = 30 Supplier, participants may be Customer, impacted by Partner, activity Investor, changes Regulator, etc. Control M The field that Used to P2I Character, Y Inspect, identifies the how determine how Selection, Regulate, information is a relationship Length = 20 Manage, used in a may be Control, participants' impacted by Influence, relationship information Monitor, Direct, changes Train, Sell, Purchase, etc. Participant M The field that Used to link the PARID Numeric, Y ID value from Object 1 contains the first two (foreign Selection, Participant ID participant object participants and key) Length = 7 Table identification key describe that relationship Participant M The field that Used to link the PARNM Character, Y Name value Object 1 contains the first two (foreign Default, from Participant Name participant object participants and key) Length = 30 Table auto- name value describe that selected based relationship on PARID Participant M The field that Used to link the PARID Numeric, Y ID value from Object 2 contains the two (foreign Selection, Participant ID second participant participants and key) Length = 7 Table object describe that identification key relationship Participant M The field that Used to link the PARNAM Character, Y Name value Object 2 contains the two (foreign Default, from Participant Name second participant participants and key) Length = 30 Table auto- object name value describe that selected based relationship on PARID Frequency Performance O The performance Used to check P2E Numeric, N Format = 99999 field that the impact from Field documents the changes to entry, number of times communication Length = 5 the participants and communicate with collaboration each other enablers Duration O The performance Used to check P2E Numeric, N Format = 99999 field that the impact from Field documents the changes to entry, duration of the communication Length = 5 communication and between collaboration participants enablers Timescale O The performance Used to check P2E Character, Y Years, months, that field the impact from Selection, weeks, days, documents the changes to Length = 8 hours, minutes, timescale of the communication seconds, etc duration field and collaboration enablers Lifecycle Lifecycle M The lifecycle field Used to check P2E Date, Y Julian Calendar; start date that identifies the relationship Field Format = YYYY/ when the of the entry, MM/DD relationship participant to Length = 10 between the two enabler objects began Lifecycle M The lifecycle field Used to check P2E Date, Y Julian Calendar; end date that identifies the relationship Field Format = YYYY/ when the of the entry, MM/DD relationship participant to Length = 10 between the two enabler objects end Enabler to Enabler Object: how One Tool Interacts with Another Tool

The enabler to enabler object describes an enterprise in terms of interactions between tools (e.g., software applications) used in the enterprise. This object references enabler objects with data that is relevant within and/or across an EAAF domain.

Any type of data may be included in the enabler to enabler object. For example, the enabler to enabler object may contain data that describes a category of the object (e.g., fully automated, semi-automated, manual), a type of the object (e.g., synchronous, asynchronous, messaging, batch processing), a relationship of enablers defined in the object (e.g., procedure, time, event, protocol), dependencies of the enablers (e.g., real-time, batch, time-based), and time value fields such as those noted above.

Table 7 shows an exemplary definition of an enabler to enabler object. Other embodiments may employ a different type of table with different fields.

TABLE 7 Field Object Reference Table Field Name Type Req Description Use Check Type Ref. Values ID General M A non-intelligent Used to Auto N value that defines uniquely number the unique “key” identify the for the database object as a record record and for relating it with other objects. Name M A non-intelligent Used to provide Character, N standard value the primary Field that describes the means of entry, object. identifying and Length = 30 searching. Description M An intelligent, Used to provide Character, N non-standard a secondary Field value that means of entry, describes the identify and Length = 255 object with detail. searching. Category Classification M The field that Used to Character, Y Fully categorizes the identify the Selection, automated, relationship relationship Length = 30 Semi- between the within the automated, enablers decision Manual, etc control domain structure. Type M The field that Used to E2A Character, Y Synchronous identifies the determine how Selection, messaging, specific type of an enabler may Length = 20 asynchronous relationship be impacted by messaging, between the changes in an batch enablers activity processing, etc Call reason Relationship M The field that Used to E2I Character, Y Data processing, identifies how determine how Selection, data storage, information is a relationship Length = 20 data validation, used in an may be data transfers, enabler's impacted by data translation, relationship information other changes Call protocol M The field that Used to E2A Character, Y real-time, describes the determine how Selection, process, event, relationship of the a relationship Length = 30 time-based, etc. enablers may be impacted by activity changes Enabler M The field that Used to link the ENAID Numeric, Y ID value from Object 1 ID contains the first two enablers (foreign Selection, the Enabler enabler object and describe key) Length = 7 Table identification key the relationship Enabler M The field that Used to link the ENANM Character, Y Name value Object 1 contains the first two enablers (foreign Default, from Enabler Name enabler object and describe key) Length = 30 Table auto- name value that selected based relationship on ENAID Enabler M The field that Used to link the ENAID Numeric, Y ID value from Object 2 ID contains the two enablers (foreign Selection, the Enabler second enabler and describe key) Length = 7 Table object that identification key relationship Enabler M The field that Used to link the ENANM Character, Y Name value Object 2 contains the two enablers (foreign Default, from Enabler Name second enabler and describe key) Length = 30 Table auto- object name value that selected based relationship on ENAID Frequency Performance O This field Used to check E2A Numeric, N Format = 99999 documents the the impact from Field number of times changes to entry, the enablers communication Length = 5 communicate with and each other collaboration enablers Duration O This field Used to check E2A Numeric, N Format = 99999 documents the the impact from Field duration of the changes to entry, communication communication Length = 5 between enablers and collaboration enablers Timescale O This field Used to check E2A Character, Y Years, months, documents the the impact from Selection, weeks, days, timescale of the changes to Length = 8 hours, minutes, duration field communication seconds, etc and collaboration enablers Volume O This field Used to E21 Numeric, N Format = 99999 documents the determine the Field volume of data impact from entry, that is exchanged changes to the Length = 5 between the information on enablers (in the enabler KB/sec) Lifecycle Lifecycle M The field that Used to check E2A Date, Y Julian Calendar; start date identifies when the relationship Field Format = YYYY/ the relationship of the enabler entry, MM/DD between the two to activity Length = 10 objects began Lifecycle end M The field that Used to check E2A Date, Y Julian Calendar; date identifies when the relationship Field Format = YYYY/ the relationship of the entry, MM/DD between the two participant to Length = 10 objects end enabler Activity to Activity Object: how One Activity Impacts Another Activity

The activity to activity object describes the enterprise's organization in terms of relationships between activities. Activities do not “call” each other, but rather have a reliance on each other in a process or a sequence of events. The activity to activity object references activity objects with data that is relevant within and/or across an EAAF domain.

Any type of data may be included in the activity to activity object. For example, the activity to activity object may contain data that describes relationships of activities in the object (e.g., time-independent, time dependent), identities of the activity objects, time value fields such as those noted above, and the like.

Table 8 shows an exemplary definition of an activity to activity object. Other embodiments may employ a different type of table with different fields.

TABLE 8 Field Object Reference Table Name Field Type Req Description Use Check Type Ref. Values ID General M A non-intelligent Used to Auto N value that defines uniquely number the unique “key” identify the for the database object as a record record and for relating it with other objects Name M A non- Used to provide Character, N intelligent the primary Field standard value means of entry, that describes identifying and Length = 30 the object searching Description M An intelligent, Used to provide Character, N non-standard a secondary Field value that means of entry, describes the identify and Length = 255 object with searching detail Category Classification M The field that Used to Character, Y Time- categorizes the identify the Selection, dependent, object relationship Length = 30 Time- relationship within the independent, etc decision control domain structure Type M The field that Used to Character Y Direct, Indirect, identifies the identify how Selection, Support, type of object the relationship Length = 20 Correlative, etc relationship is used by the objects for the performance of an activity Reliance Relationship M The field that Used to Character Y Analysis, describes the determine the Selection, Control, relationship of dependency of Length = 30 Decision- the activity the activity making, Process objects object execution, etc. relationships Activity M The field that Used to link the ACTID Numeric, Y ID value from Object 1 contains the first two activity (foreign Selection, Activity Table ID activity object objects and key) Length = 7 identification describe the key relationship Activity M The field that Used to link the ACTNM Character Y Name value Object 1 contains the first two activity (foreign Default, from Activity Name activity object objects and key) Length = 30 Table auto- name value describe the selected based relationship on ACTID Activity M The field that Used to link the ACTID Numeric, Y ID value from Object 2 contains the two activity (foreign Selection, Activity Table ID second activity objects and key) Length = 7 object describe the identification relationship key Activity M The field that Used to link the ACTNAM Character, Y Name value Object 2 contains the two activity (foreign Default, from Activity Name second activity objects and key) Length = 30 Table auto- object name describe the selected based value relationship on ACTID Lifecycle Lifecycle M The field that Used to check E2A Date, Y Julian Calendar; start date identifies when the relationship Field Format = YYYY/ the relationship of the enabler entry, MM/DD between the two to activity Length = 10 objects began Lifecycle M The field that Used to check E2A Date, Y Julian Calendar; end date identifies when the relationship Field Format = YYYY/ the relationship of the enabler entry, MM/DD between the two to activity Length = 10 objects end

FIG. 3 a shows an example of common object relationships across different decision control domains 30, 31 and 31. The I2I relationship structure 37 of FIG. 3 a shows how information relates across the three domains; and the P2P relationship structure 38 of FIG. 3 a shows how participants relate to one another across the domains. For example, in the I2I structure, information 34 relating to regional sales may include information 35 relating to sales to a customer and information 36 relating to sales to a distributor. In turn, information 35 and 36 may relate to information in domain 32.

FIG. 3 b shows common object relationships in a single domain. For example, the E2E relationship structure 40 shows how various Web-related applications are employed in an online transaction. Web application 41 is used to purchase a product that is displayed by Web catalog 42 and configurator 42. Web application pay pal 45 is used to collect payment and other information for the purchase, and to generate a sales order 46.

Cross-Object Relationships

Cross-object relationships within the EAAF database describe “the how” and “the why” of objects relationships, i.e., the purpose of their relationship. The EAAF stores cross-object relationship objects that interrelate different types of core objects in the EAAF database. The cross-object relationship objects are defined by tables that contain data defining an object's integration and dependency on another object based on specific environmental condition(s). The cross-object relationships objects also reflect how varying influences and changing conditions impact cross-object dependencies. Cross-object relationships do not cross decision-control domains.

The cross-object relationships are depicted conceptually in FIG. 4. As noted above, cross-object relationship objects include participant to information (P2I) object 20, participant to enabler (P2E) object 21, participant to activity (P2A) object 22, enabler to information (E2I) object 24, enabler to activity (E2A) object 25, and activity to information (A2I) object 26. Other embodiments may employ different types and numbers of objects.

Enabler to Activity Object: What Enables the Activity

The activity to enabler object describes which tools (enablers) perform a particular process (activity). Any type of data may be included in the enabler to activity object. For example, the enabler to activity object may contain data that describes the subject activity and enabler objects, a type of the activity referenced in the activity to enabler object (e.g., fully automated, partially automated, not automated), expected duration, and frequency.

Table 9 shows an exemplary definition of an enabler to activity object. Other embodiments may employ a different type of table with different fields.

TABLE 9 Field Object Reference Table Field Name Type Req Description Use Check Type Ref. Values ID General M A non-intelligent Used to Auto N value that defines uniquely number the unique “key” identify the for the database object as a record record and for relating it with other objects Name M A non-intelligent Used to provide Character, N standard value the primary Field that describes the means of entry, object identifying and Length = 30 searching Description M An intelligent, Used to provide Character, N non-standard a secondary Field value that means of entry, describes the identify and Length = 255 object with detail searching Category Classification M The field that Used to A2I Character, Y Interactive, describes how the determine Selection, Active, Passive, enabler interacts improvements Length = 15 etc. with the activity to the for automation information transformation Type M The field that Used to A2I Character, Y Fully describes the level determine the Selection, automated, of automation the improvements Length = 15 Partially enabler provides to the activity automated, Un- via automation automated, etc. Enabler Relationship M The field that Used to link the ENAID Numeric, Y ID value from Object ID contains the two objects and (foreign Selection, the Enabler enabler object describe that key) Length = 7 Table identification key relationship Enabler M The field that Used to link the ENANAM Character, Y Name value Object Name contains the two objects and (foreign Default, from Enabler enabler object describe that key) Length = 30 Table auto- name value relationship selected based on ENAID Activity M The field that Used to link the ACTID Numeric, Y ID value from Object ID contains the two objects and (foreign Selection, the Activity activity object describe that key) Length = 7 Table identification key relationship Activity M The field that Used to link the ACTNAM Character, Y Name value Object Name contains the two objects and (foreign Default, from Activity activity object describe that key) Length = 30 Table auto- name value relationship selected based on ACTID Frequency Performance O The field Used to check P2A Numeric, N Format = 99999 documents the the enabler's Field number of times ability to entry, the enabler is support the Length = 5 executes within participant in an activity their activity execution execution Duration O The field Used to check P2A Numeric, N Format = 99999 documents the the enabler's Field duration the ability to entry, enabler executes support the Length = 5 logic to automate participant in an activity their activity execution Timescale O The performance Used to check P2A Character, Y Years, months, field that the enabler's Selection, weeks, days, documents the ability to Length = 8 hours, minutes, timescale of the support the seconds, etc duration field participant in their activity execution Lifecycle Lifecycle M The field that Used to check P2A Date, Y Julian Calendar; start date identifies when the relationship Field Format = YYYY/ the relationship of the entry, MM/DD between the two participant to Length = 10 objects began activity Lifecycle end M The field that Used to check P2A Date, Y Julian Calendar; date identifies when the relationship Field Format = YYYY/ the relationship of the entry, MM/DD between the two participant to Length = 10 objects end activity Participant to Information Object: What Decision a Participant Makes Using Information

The participant to information object specifies a decision that is made by a participant referenced in the object based on information referenced in the object. Any type of data may be included in the participant to information object. For example, the participant to information object identifies the subject participant and information objects, a type of the decision made by the participant (e.g., automated, manual, other), a medium (e.g., computer, TV, telephone, newspaper) on which the information is contained, and the like. The participant to information object provides data that is structured in a format that is representative of a current state of affairs or events, i.e., relevancy, and is accurate in terms of the time value or sensitivity.

Table 10 shows an exemplary definition of a participant to information object. Other embodiments may employ a different type of table with different fields.

TABLE 10 Field Object Reference Table Field Name Type Req Description Use Check Type Ref. Values ID General M A non-intelligent Used to Auto N value that defines uniquely number the unique “key” identify the for the database object as a record record and for relating it with other objects Name M A non-intelligent Used to provide Character, N standard value the primary Field that describes the means of entry, object identifying and Length = 30 searching Description M An intelligent, Used to provide Character, N non-standard a secondary Field value that means of entry, describes the identify and Length = 255 object with detail searching Category Classification M The field that It describes Character, Y Content owner, categorizes the how a Selection, Content participant to Participant Length = 30 processor, information relates to an Structure owner, relationship information etc. Type M The field that Used to check E2I Character, Y Fully describes whether on the enabler Selection, automated, the relationship is to information Length = 20 Semi- automated by an relationship automated, enabler (tool) Manual, etc. Decision Impact M The field that Used to check E2I Boolean N Yes, No Object indicates whether the enabler's the participant decision makes a decision support capability for the participant Criticality O The field that Used to check E2I Character, Y Business describes the on the enabler Selection, critical, Program value of the to information Length = 25 critical, Project information to the relationship critical, participant in how Operation it affects the critical, participant Decision critical, Non- critical, etc. Medium Relationship M The field that Used to check E2I Character, Y Computer, defines the on the enabler Selection, Report, medium by which to information Length = 30 Document, the participant relationship T.V., Drawing, interacts with the Internet, information Telephone, Radio, Print media, etc. Participant M The field that Used to link the PARID Numeric, Y ID value from Object ID contains the two objects and (foreign Selection, the Participant participant object describe the key) Length = 7 Table identification key relationship Participant M The field that Used to link the PARNAM Character, Y Name value Object Name contains the two objects and (foreign Default, from Participant participant object describe that key) Length = 30 Table auto- name value relationship selected based on PARID Information M The field that Used to link the INFID Numeric, Y ID value from Object ID contains the two objects and (foreign Selection, the Information information object describe that key) Length = 7 Table identification key relationship Information Relationship M The field that Used to link the INFNAM Character, Y Name value Object Name contains the two objects and (foreign Default, from information object describe that key) Length = 30 Information name value relationship Table auto- selected based on INFID Periodicity - Control O The field that Used to check P2A Character, Y Bi-annual, Yearly defines the the relationship Selection, Annual, Semi- requirement of the Length = 20 annual, regarding information's Quarterly, etc. availability and timing with control respect to the activity Periodicity - O The field that Used to check P2A Character, Y Bi-monthly, Monthly defines the the relationship Selection, Monthly, Semi- requirement of the Length = 20 monthly, etc regarding information's availability and timing with control respect to the activity Periodicity - O The field that Used to check P2A Character, Y Bi-Weekly, Weekly defines the the relationship Selection, Weekly, Semi- requirement of the Length = 20 Weekly, etc. regarding information's availability and timing with control respect to the activity Periodicity - O The field that Used to check P2A Character, Y Once Daily, Daily defines the the relationship Selection, Twice Daily, requirement of the Length = 20 Three Times regarding information's Daily, etc. availability and timing with control respect to the activity Periodicity - O The field that Used to check P2A Character, Y Hourly, By the Time defines the the relationship Selection, minute, By the requirement of the Length = 20 second, etc. regarding information's availability and timing with control respect to the activity Frequency Performance O The performance Used to check E2I; P2A Numeric, N Format = 99999 field documents the impact from Field the number of changes to entry, times the activity and Length = 5 participants uses collaboration the information to enablers control an activity Duration O The performance Used to check E2I; P2A Numeric, N Format = 99999 field documents the impact from Field the use duration changes to entry, of the information activity and Length = 5 by the collaboration participants enablers Timescale O The performance Used to check E2I; P2A Character, Y Years, months, field that the impact from Selection, weeks, days, documents the changes to Length = 8 hours, minutes, timescale of the communication seconds, etc duration field and collaboration enablers Lifecycle Lifecycle M The field that Used to check E2I Date, Y Julian Calendar; start date identifies when the relationship Field Format = YYYY/ the relationship of the enabler entry, MM/DD between the two to Information Length = 10 objects began Lifecycle end M The field that Used to check E2I Date, Y Julian Calendar; date identifies when the relationship Field Format = YYYY/ the relationship of the enabler entry, MM/DD between the two to Information Length = 10 objects end Participant to Activity Object: why the Participant is Performing the Activity

The participant to activity object describes why the participant referenced in the object is performing the activity referenced in the object. Any type of data may be included in the participant to information object. For example, the information may specify the subject participant and activity objects, a category of the activity (e.g., active, passive, other), a type of the participant (e.g., individual, team, other), a role of the participant (e.g., facilitator, supervisor, executor, etc.), performance of the participant (e.g., expected execution duration), and frequency of execution of the activity referenced in the object.

Table 11 shows an exemplary definition of a participant to activity object. Other embodiments may employ a different type of table with different fields.

TABLE 11 Field Object Reference Table Field Name Type Req Description Use Check Type Ref. Values ID General M A non-intelligent Used to Auto N value that defines uniquely number the unique “key” identify the for the database object as a record record and for relating it with other objects Name M A non-intelligent Used to Character, N standard value provide the Field that describes the primary entry, object means of Length = 30 identifying and searching Description M An intelligent, Used to Character, N non-standard provide a Field value that secondary entry, describes the means of Length = 255 object with detail identify and searching Category Classification M The field that Used to E2A Character, Y Fully describes whether check on the Selection, automated, the relationship is enabler to Length = 20 Semi- automated by an activity automated, enabler (tool) relationship Manual, etc. Type M The field that Used to P2P Character, Y Individual, defines the check on the Selection, Team member, relationship of the participant to Length = 20 Alliance participant to participant member, Work activity relationship crew, etc. Role Relationship M This field defines Used to P2P Character, Facilitator, the role the check on the Selection, Mentor participant is participant to Length = 20 Supervisor, engaged with participant Worker, Trade respect to the relationship Partner, etc. performing the activity Participant M The field that Used to link PARID Numeric, Y ID value from Object ID contains the the two (foreign key) Selection, the Participant participant object objects and Length = 7 Table identification key describe the relationship Participant M The field that Used to link PARNAM Character, Y Name value Object Name contains the the two (foreign key) Default, from Participant participant object objects and Length = 30 Table auto- name value describe that selected based relationship on PARID Activity M The field that Used to link ACTID Numeric, Y ID value from Object ID contains the the two (foreign key) Selection, the Activity activity object objects and Length = 7 Table identification key describe that relationship Activity M The field that Used to link ACTNAM Character, Y Name value Object Name contains the the two (foreign key) Default, from Activity activity object objects and Length = 30 Table auto- name value describe that selected based relationship on ACTID Periodicity - Control O The field that Used to P2A Character, Y Bi-annual, Yearly defines the check the Selection, Annual, Semi- requirement relationship Length = 20 annual, regarding of the Quarterly, etc. availability and information's control timing with respect to the activity Periodicity - Control O The field that Used to P2A Character, Y Bi-monthly, Monthly defines the check the Selection, Monthly, Semi- requirement relationship Length = 20 monthly, etc regarding of the availability and information's control timing with respect to the activity Periodicity - O The field that Used to P2A Character, Y Bi-Weekly, Weekly defines the check the Selection, Weekly, Semi- requirement relationship Length = 20 Weekly, etc. regarding of the availability and information's control timing with respect to the activity Periodicity - O The field that Used to P2A Character, Y Once Daily, Daily defines the check the Selection, Twice Daily, requirement relationship Length = 20 Three Times regarding of the Daily, etc. availability and information's control timing with respect to the activity Periodicity - O The field that Used to P2A Character, Y Hourly, By the Time defines the check the Selection, minute, By the requirement relationship Length = 20 second, etc. regarding of the availability and information's control timing with respect to the activity Frequency Performance O The field Used to E2A Numeric, N Format = 99999 documents the check the Field number of times enabler's entry, the participant ability to Length = 5 executes the support the activity participant in their activity performing Duration O The field Used to E2A Numeric, N Format = 99999 documents the check the Field participant's enabler's entry, duration for ability to Length = 5 executing the support the activity including participant in thought and break their activity time performing Timescale O The performance Used to E2A Character, Y Years, months, field that check the Selection, weeks, days, documents the enabler's Length = 8 hours, minutes, timescale of the ability to seconds, etc duration field support the participant in their activity performing Lifecycle Lifecycle M The field that Used to E2A Date, Y Julian Calendar; start date identifies when check the Field Format = YYYY/ the relationship relationship entry, MM/DD between the two of the enabler Length = 10 objects began to activity Lifecycle end M The field that Used to E2A Date, Y Julian Calendar; date identifies when check the Field Format = YYYY/ the relationship relationship entry, MM/DD between the two of the enabler Length = 10 objects end to activity Participant to Enabler Object: how the Participant Uses the Tool

The participant to enabler object describes how the participant referenced in the object uses the enabler (tool) referenced in the object. Any type of data may be included in the participant to enabler object. For example, the information may specify the subject participant and enabler objects, as well as the other information noted below.

Table 12 shows an exemplary definition of a participant to enabler object. Other embodiments may employ a different type of table with different fields.

TABLE 12 Field Object Reference Table Field Name Type Req Description Use Check Type Ref. Values ID General M A non-intelligent Used to Auto N value that defines uniquely number the unique “key” identify the for the database object as a record record and for relating it with other objects Name M A non-intelligent Used to Character, N standard value provide the Field that describes the primary entry, object means of Length = 30 identifying and searching Description M An intelligent, Used to Character, N non-standard provide a Field value that secondary entry, describes the means of Length = 255 object with detail identify and searching Category Classification M The field that Used to E2A Character, Y Active, Passive, describes whether check on the Selection, etc. the relationship is enabler to Length = 15 automated by an activity enabler (tool) relationship Type M The field that Used to E2A Character, Y Information defines the define the Selection, access, relationship of the purpose of Length = 25 Information participant to the presentation, enabler with relationship Activity respect to the between the execution, activity performed objects for Activity while using the checking analysis, etc. enabler activity support Presentation Interface M The field that Used to E2I Character, Y Presentation defines the check the Selection, server, Desktop, participant to the relationship Length = 20 Web browser, enabler and support Terminal, etc. relationship with of the enabler respect the to the exchange information mechanism required Protocol M The field that Used to E2E Character, Y FTP, LAN, defines the check the Selection, WAN, WAP, participant to the relationship Length = 20 Satellite, enabler and support WWW, etc. relationship with between respect the enablers to exchange medium communicate Support Impact O The field that Used to P2A Time, N Format = HH:MM:SS Level identifies the time check the Field value of the participant's entry, participant's ability to Length = 6 activity execute the activity Productivity O The field that Used to P2A Boolean N Yes, No Impact identifies the determine the impact to the impact to the participant's participant's productivity activity execution Participant Relationship M The field that Used to link PARID Numeric, Y ID value from Object ID contains the the two (foreign key) Selection, the Participant participant object objects and Length = 7 Table identification key describe the relationship Participant Relationship M The field that Used to link PARNAM Character, Y Name value Object Name contains the the two (foreign key) Default, from Participant participant object objects and Length = 30 Table auto- name value describe that selected based relationship on PARID Enabler M The field that Used to link ENAID Numeric, Y ID value from Object ID contains the the two (foreign key) Selection, the Enabler enabler object objects and Length = 7 Table identification key describe that relationship Enabler M The field that Used to link ENANAM Character, Y Name value Object Name contains the the two (foreign key) Default, from Enabler enabler object objects and Length = 30 Table auto- name value describe that selected based relationship on ENAID Hours per Availability O The field that Used to P2A Time, N Format = HH:MM:SS Day defines the check the Field requirement participant's entry, regarding the requirement Length = 6 enabler's for activity availability execution Days per O The field that Used to P2A Numeric, N Format = 9 week defines the check the Field requirement participant's entry, regarding the requirement Length = 1 enabler's for activity availability execution Days per O The field that Used to P2A Numeric, N Format = 99 Month defines the check the Field requirement participant's entry, regarding the requirement Length = 2 enabler's for activity availability execution Days per O The field that Used to P2A Numeric, N Format = 999 Year defines the check the Field requirement participant's entry, regarding the requirement Length = 3 enabler's for activity availability execution Frequency Performance O The field Used to P2A Numeric, N Format = 99999 documents the check the Field number of times enabler's entry, the participant ability to Length = 5 executes the logic support the in the enabler participant in their activity execution Duration O The field Used to P2A Numeric, N Format = 99999 documents the check the Field participant's enabler's entry, duration for ability to Length = 5 executing the support the enabler's logic participant in their activity execution Timescale O The performance Used to P2A Character, Y Years, months, field that check the Selection, weeks, days, documents the enabler's Length = 8 hours, minutes, timescale of the ability to seconds, etc duration field support the participant in their activity execution Lifecycle Lifecycle M The field that Used to P2A Date, Y Julian Calendar; start date identifies when check the Field Format = YYYY/ the relationship relationship entry, MM/DD between the two of the Length = 10 objects began participant to activity Lifecycle M The field that Used to P2A Date, Y Julian Calendar; end date identifies when check the Field Format = YYYY/ the relationship relationship entry, MM/DD between the two of the Length = 10 objects end participant to activity Enabler to Information Object: how the Information is Transformed by the Enabler

The enabler to information object describes how information referenced in the object is transformed by a tool referenced in the object. One of the objectives of this object is to identify methods contained within the enabler object that are deployed within an enterprise and that are used to transform information from one state to another, or from one medium to another. A time variable contained within the object description table is used to determine if different enablers transform information between states at a consistent rate. This time variable indicates how effectively the enabler will be able to support increases in activities (i.e., load) that the enabler has automated.

Any type of data may be included in the enabler to information object. For example, the object may include a category of the information relative to the enabler (e.g., input or output), a type of the information (e.g., data, voice feed, algorithm, video feed), an initial state of the information (e.g., before processing), a final state of the information (e.g., after processing), performance data (e.g., duration of a call), and frequency data (e.g., exchange volume per call).

Table 13 shows an exemplary definition of an enabler to information object. Other embodiments may employ a different type of table with different fields.

TABLE 13 Field Object Reference Table Field Name Type Req Description Use Check Type Ref. Values ID General M A non-intelligent Used to Auto N value that defines uniquely number the unique “key” identify the for the database object as a record record and for relating it with other objects Name M A non-intelligent Used to Character, N standard value provide the Field that describes the primary entry, object means of Length = 30 identifying and searching Description M An intelligent, Used to Character, N non-standard provide a Field value that secondary entry, describes the means of Length = 255 object with detail identify and searching Category Classification The field that Used to A2I: Character, Y Input, Output, identifies the check the I2I Selection, etc. relationship to the requirement Length = 8 physical activity for enabling the information transformation for an acitvity Type M The field that Used to A2I; Character, Y Audio, Video, identifies the validate the I2I Selection, Digital enabler's technology to Length = 10 Graphics, technology that enable Drawing, will be used to automation Electronic manage the of the Document, information object activity and Physical its Document, etc. transformation of the information object Before State M The field that Used to A2I; P2I; Numeric, N Format = 999 processing identifies the check the I2I Field e.g. initial state of the information entry, 000, 001, 002, information object relevancy Length = 3 003 000 means prior to its and the that this info transformation via participant's does not yet the activity requirement exist and the for enabler supports controlling a creation the event process. process After M The field that Used to A2I; P2I; Numeric, N Format = 999 Processing identifies the check the I2I Field e.g. “state initial state of the information entry, before information object relevancy Length = 3 processing” + 1, after its and the so: 001, 002, 003, transformation via participant's 004 . . . n + 1 the activity requirement for controlling the event process Enabler Relationship M The field that Used to link ENAID Numeric, Y ID value from Object ID contains the the two (foreign key) Selection, the Enabler enabler object objects and Length = 7 Table identification key describe that relationship Enabler M The field that Used to link ENANAM Character, Y Name value Object Name contains the the two (foreign key) Default, from Enabler enabler object objects and Length = 30 Table auto- name value describe that selected based relationship on ENAID Information M The field that Used to link INFID Numeric, Y ID value from Object ID contains the the two (foreign key) Selection, the Information information object objects and Length = 7 Table identification key describe that relationship Information M The field that Used to link INFNAM Character, Y Name value Object Name contains the the two (foreign key) Default, from information object objects and Length = 30 Information name value describe that Table auto- relationship selected based on INFID Frequency Performance O This field Used to A2I; Numeric, N Format = 99999 documents the check the I2I Field number of times performance entry, the enabler of the enabler Length = 5 executes its logic required to to manage the manage the information object information object transformation Duration O This field Used to A2I; Numeric, N Format = 99999 documents the check the I2I Field duration of the performance entry, enabler's logic to of the enabler Length = 5 manage the required to information object manage the information object transformation Timescale O This field Used to A2I; Character, Y Years, months, documents the check the I2I Selection, weeks, days, timescale of the performance Length = 8 hours, minutes, duration field of the enabler seconds, etc required to manage the information object transformation Volume O This field Used to A2I; Numeric, N Format = 99999 documents the check the I2I Field volume of performance entry, information that is of the enabler Length = 5 managed by the required to enabler for the manage the activity execution information object transformation Lifecycle Lifecycle M The field that Used to A2I Date, Y Julian Calendar; start date identifies when check the Field Format = YYYY/ the relationship relationship entry, MM/DD between the two of the Length = 10 objects began activity to information Lifecycle end M The field that Used to A2I Date, Y Julian Calendar; date identifies when check the Field Format = YYYY/ the relationship relationship entry, MM/DD between the two of the Length = 10 objects end activity to information Activity to Information Object: why the Information is Transformed by the Activity

The participant to enabler object describes why information referenced in the object is transformed by the activity referenced in the object. Essentially, this cross-object relationship table provides a connection between an event and information about the event. Any type of data may be included in the activity to information object. For example, the object may specify the subject activity and information objects, category information relating to the activity (e.g., active, passive, other), a type of the activity (e.g., processing, validation), as well as the other information noted below.

Table 14 shows an exemplary definition of an activity to information object. Other embodiments may employ a different type of table with different fields.

TABLE 14 Field Object Reference Table Field Name Type Req Description Use Check Type Ref. Values ID General M A non-intelligent Used to Auto N value that defines uniquely number the unique “key” identify the for the database object as a record record and for relating it with other objects Name M A non-intelligent Used to Character, N standard value provide the Field that describes the primary entry, object means of Length = 30 identifying and searching Description M An intelligent, Used to Character, N non-standard provide a Field value that secondary entry, describes the means of Length = 255 object with detail identify and searching Category Classification The field that Used to E2I; Character, Y Interactive, identifies the validate the E2A Selection, Active, Passive, relationship to the information Length = 15 etc. physical activity that transformed by an activity automated by an enabler Type M The field that Used to E2I; Character, Y Activity identifies the validate the E2A Selection, Processing, activity that information Length = 12 Validation, transforms the that Trading, information object transformed Evaluation, by an activity Reference, etc. automated by an enabler Before State M The field that Used to E2I; P2A; Numeric, N Format = 999 processing identifies the check the I2I Field e.g. initial state of the information entry, 000, 001, 002, information object relevancy Length = 3 003 000 means prior to its and the that this info transformation via participant's does not yet the activity requirement exist and the for enabler supports controlling a creation the event process. process After M The field that Used to A2I; P2I; Numeric, N Format = 999 Processing identifies the check the I2I Field e.g. “state initial state of the information entry, before information object relevancy Length = 3 processing” + 1, after its and the so: 001, 002, 003, transformation via participant's 004 . . . n + 1 the activity requirement for controlling the event process Activity Relationship M The field that Used to link ACTID Numeric, Y ID value from Object ID contains the the two (foreign key) Selection, the Activity activity object objects and Length = 7 Table identification key describe that relationship Activity M The field that Used to link ACTNAM Character, Y Name value Object Name contains the the two (foreign key) Default, from Activity activity object objects and Length = 30 Table auto- name value describe that selected based relationship on ACTID Information M The field that Used to link INFID Numeric, Y ID value from Object ID contains the the two (foreign key) Selection, the Information information object objects and Length = 7 Table identification key describe that relationship Information Relationship M The field that Used to link INFNAM Character, Y Name value Object Name contains the the two (foreign key) Default, from information object objects and Length = 30 Information name value describe that Table auto- relationship selected based on INFID Frequency Performance O This field Used to E2I; Numeric, N Format = 99999 documents the check the I2I Field number of times performance entry, the activity is of the enabler Length = 5 performed when required to transforming the transform the information object information object Duration O This field Used to E2I; Numeric, N Format = 99999 documents the check the I2I Field duration of the performance entry, activity when of the enabler Length = 5 transforming the required to information object transform the information object Timescale O This field Used to E2I; Character, Y Years, months, documents the check the I2I Selection, weeks, days, timescale of the performance Length = 8 hours, minutes, duration field of the enabler seconds, etc required to transform the information object Volume O This field Used to E2I; Numeric, N Format = 99999 documents the check the I2I Field volume of performance entry, information that is of the enabler Length = 5 transformed by required to the activity transform the information object Lifecycle Lifecycle M The field that Used to E2I Date, Y Julian Calendar; start date identifies when check the Field Format = YYYY/ the relationship relationship entry, MM/DD between the two of the Length = 10 objects began activity to information Lifecycle end M The field that Used to E2I Date, Y Julian Calendar; date identifies when check the Field Format = YYYY/ the relationship relationship entry, MM/DD between the two of the Length = 10 objects end activity to information

Value Objects

Value objects define, e.g., objectives, benefits, metrics, influences, settings, and domains within the EAAF database. The value objects may be used to complement the information in a cell or process scenario. For example, these objects may be used to specify how different process scenarios generate value to the enterprise. Furthermore, value objects may be used to define environmental settings in which process scenarios are constructed and influences that impact such process scenarios.

Enterprise Objectives

The enterprise objectives object links enterprise strategies, goals and objectives in a single record, and may be used to align an initiative to a specific enterprise objective. Any type of data may be included in the enterprise objectives object.

Table 15 shows an exemplary definition of an enterprise objectives object. Other embodiments may employ a different type of table with different fields.

TABLE 15 Field Object Reference Table Field Name Type Req Description Use Check Type Ref. Values ID General M A non-intelligent Used to Auto N value that defines uniquely number the unique “key” identify the for the database object as a record record and for relating it with other objects Name M A non-intelligent Used to provide Character, N standard value the primary Field that describes the means of entry, object identifying and Length = 30 searching Description M An intelligent, Used to provide Character, N non-standard a secondary Field value that means of entry, describes the identify and Length = 255 object with detail searching Category Classification M The field Used to classify Character, Y Predefined indicates the the objective Selection, reference table category of the Length = 15 values objective Type M The field Used to classify Character, Y Predefined indicates the type the objective Selection, reference table of the objective Length = 15 values Criticality M The field that Used to classify Character, Y Business describes the the objective Selection, critical, Program criticality of the Length = 25 critical, Project objective critical, Operation critical, Decision critical, Non- critical, etc. Lifecycle Lifecycle M The field that Used to provide Date, Y Julian Calendar; start date identifies when a window of Field Format = YYYY/ the objective was opportunity for entry, MM/DD formulated the objective Length = 10 Lifecycle end M The field that Used to provide Date, Y Julian Calendar; date identifies when a window of Field Format = YYYY/ the objective is opportunity for entry, MM/DD slated to terminate the objective Length = 10 Enterprise Benefits

The enterprise benefits object links enterprise performance groups with expected benefits. Any type of data may be included in the enterprise benefits object.

Table 16 shows an exemplary definition of an enterprise benefits object. Other embodiments may employ a different type of table with different fields.

TABLE 16 Field Object Reference Table Field Name Type Req Description Use Check Type Ref. Values ID General M A non-intelligent Used to Auto N value that defines uniquely number the unique “key” identify the for the database object as a record record and for relating it with other objects Name M A non-intelligent Used to provide Character, N standard value the primary Field that describes the means of entry, object identifying and Length = 30 searching Description M An intelligent, Used to provide Character, N non-standard a secondary Field value that means of entry, describes the identify and Length = 255 object with detail searching Category Classification M The field Used to classify Character, Y Predefined indicates the the benefit Selection, reference table category of the Length = 15 values benefit Type M The field Used to classify Character, Y Predefined indicates the type the benefit Selection, reference table of the benefit Length = 15 values Criticality M The field that Used to classify Character, Y Business describes the the benefit Selection, critical, Program criticality of the Length = 25 critical, Project benefit critical, Operation critical, Decision critical, Non- critical, etc. Lifecycle Lifecycle M The field that Used to provide Date, Y Julian Calendar; start date identifies when a window of Field Format = YYYY/ the benefits would opportunity for entry, MM/DD begin the benefit Length = 10 Lifecycle end M The field that Used to provide Date, Y Julian Calendar; date identifies when a window of Field Format = YYYY/ the benefits would opportunity for entry, MM/DD end the benefit Length = 10 Performance Metrics

The performance metrics object specifies performance metrics that are representative of a specific industry, trade, and/or governmental performance benchmark. The performance metrics include performance standards that are used for comparison of results from executed process scenarios with results generated from value formulas. The value formulas (defined below) are used for measuring performance results to compare against the industry, trade and/or governmental performance benchmarks, and influence actions to take to move toward the performance benchmarks.

Table 17 shows an exemplary definition of a performance metrics object. Other embodiments may employ a different type of table with different fields.

TABLE 17 Field Object Reference Table Field Name Type Req Description Use Check Type Ref. Values ID General M A non-intelligent Used to Auto N value that defines uniquely number the unique “key” identify the for the database object as a record record and for relating it with other objects Name M A non-intelligent Used to provide Character, N standard value the primary Field that describes the means of entry, object identifying and Length = 30 searching Description M An intelligent, Used to provide Character, N non-standard a secondary Field value that means of entry, describes the identify and Length = 255 object with detail searching Category Classification M The field Used to classify Character, Y Predefined indicates the the performance Selection, reference table category of the metric Length = 15 values performance metric Type M The field Used to classify Character, Y Predefined indicates the type the performance Selection, reference table of the metric Length = 15 values performance metric Criticality M The field that Used to classify Character, Y Business describes the the performance Selection, critical, Program criticality of the metric Length = 25 critical, Project performance critical, metric Operation critical, Decision critical, Non- critical, etc. Lifecycle Lifecycle M The field that Used to provide Date, Y Julian Calendar; start date identifies when a window of Field Format = YYYY/ the performance opportunity for entry, MM/DD metrics would the performance Length = 10 begin metric Lifecycle end M The field that Used to provide Date, Y Julian Calendar; date identifies when a window of Field Format = YYYY/ the performance opportunity for entry, MM/DD metrics would end the performance Length = 10 metric Environmental Settings

The environmental settings object identifies internal and external settings that exist and that drive process scenarios. Environmental factors, when related together in a unique combination, define the setting or condition in which the enterprise operates, and which the enterprise overcomes to build a system of elements that deliver value to customers and that return value to investors.

Table 18 shows an exemplary definition of an environmental settings object. Other embodiments may employ a different type of table with different fields.

TABLE 18 Field Object Reference Table Field Name Type Req Description Use Check Type Ref. Values ID General M A non-intelligent Used to Auto N value that defines uniquely number the unique “key” identify the for the database object as a record record and for relating it with other objects Name M A non-intelligent Used to provide Character, N standard value the primary Field that describes the means of entry, object identifying and Length = 30 searching Description M An intelligent, Used to provide Character, N non-standard a secondary Field value that means of entry, describes the identify and Length = 255 object with detail searching Category Classification M The field Used to classify Character, Y Legal, Societal, indicates the the Selection, Physical, category of the environmental Length = 25 Cultural, environmental setting Economic, setting Terrestrial Commerce, etc. Type M The field Used to classify Character, Y Regulations, indicates the type the Selection, Education, of the environmental Length = 35 Laws, Religion, environmental setting Weather, setting Terrain, Economy, Language, etc. Criticality M The field that Used to classify Character, Y Business describes the the Selection, critical, Program criticality of the environmental Length = 25 critical, Project environmental setting critical, setting Operation critical, Decision critical, Non- critical, etc. Lifecycle Lifecycle M The field that Used to provide Date, Y Julian Calendar; start date identifies when a window of Field Format = YYYY/ the environmental opportunity for entry, MM/DD settings would the Length = 10 begin environmental setting Lifecycle end M The field that Used to provide Date, Y Julian Calendar; date identifies when a window of Field Format = YYYY/ the environmental opportunity for entry, MM/DD settings would the Length = 10 end environmental setting Influences

This object specifies sources and types of influences that impact the enterprise. Identifying and defining influences that drive different enterprise dimensions is helpful to understanding why and how such dimensions differ. This enables the enterprise to properly compare results from different process scenarios and to determine the arrangement of cells in a process scenario that provides the greatest value to the enterprise.

Table 19 shows an exemplary definition of an influences object. Other embodiments may employ a different type of table with different fields.

TABLE 19 Field Object Reference Table Field Name Type Req Description Use Check Type Ref. Values ID General M A non-intelligent Used to Auto N value that defines uniquely number the unique “key” identify the for the database object as a record record and for relating it with other objects Name M A non-intelligent Used to provide Character, N standard value the primary Field that describes the means of entry, object identifying and Length = 30 searching Description M An intelligent, Used to provide Character, N non-standard a secondary Field value that means of entry, describes the identify and Length = 255 object with detail searching Source Classification M The field Used to classify Character, Y Political, Legal, indicates the the influence Selection, Social, source of the Length = 25 Economic, influence Regulatory, Environmental, Technology, etc. Type M The field Used to classify Character, Y Direct, Indirect, indicates the type the influence Selection, Cumulative, etc. of the influence Length = 35 Impact M The field that Used to classify Character, Y Image, describes the the influence Selection, Business, impact of the Length = 25 Financial, influence Trade, Conduct, Decision Operation, etc. Lifecycle Lifecycle M The field that Used to provide Date, Y Julian Calendar; start date identifies when a window of Field Format = YYYY/ the influences opportunity for entry, MM/DD would begin the influence Length = 10 Lifecycle end M The field that Used to provide Date, Y Julian Calendar; date identifies when a window of Field Format = YYYY/ the influences opportunity for entry, MM/DD would end the influence Length = 10 Domains: the Layers of the EAAF Database

Linked cells in a single decision-control domain comprise a single layer of the EAAF database. Each such layer encompasses the domain of authority a participant controls and the span of information a participant uses to make a decision or act upon information. The EAAF database is designed to capture common and cross object relationships at different levels of decision-control for the participant.

Each construct layer of the EAA Framework represents a decision-control domain, defined by the intersection of the decision, control, and authority for a class or type of participant and, the span of information access for that class or type of participant. These domains are “stacked” together to complete the EAA Framework, as shown, e.g., in FIG. 8. In FIG. 8, the decision control domains 80, 81 and 82 are stacked, with various objects (e.g., 84) depicted. The stacking provides an integrated view and decomposition of enterprise's participants, their information, and processes for dynamic modeling.

Table 20 shows an exemplary definition of a domain object. Other embodiments may employ a different type of table with different fields.

TABLE 20 Field Object Reference Table Field Name Type Req Description Use Check Type Ref. Values ID General M A non-intelligent Used to Auto N value that defines uniquely number the unique “key” identify the for the database object as a record record and for relating it with other objects Name M A non-intelligent Used to provide Character, N standard value the primary Field that describes the means of entry, object identifying and Length = 30 searching Description M An intelligent, Used to provide Character, N non-standard a secondary Field value that means of entry, describes the identify and Length = 255 object with detail searching Standard Classification M The field Used to classify Character, Y Industry, indicates whether the influence Selection, Scientific, the domain is Length = 25 Trade, Business, associated with a Public, standards Customer, organization Government, etc. Lifecycle Lifecycle M The field that Used to provide Date, Y Julian Calendar; start date identifies when a window of Field Format = YYYY/ the influences opportunity for entry, MM/DD would begin the influence Length = 10 Lifecycle end M The field that Used to provide Date, Y Julian Calendar; date identifies when a window of Field Format = YYYY/ the influences opportunity for entry, MM/DD would end the influence Length = 10 Value Element Object

The value element defines the value of information that is transformed during a process scenario. In this regard, to identify value in process scenario, a measurement point in the process scenario is selected. This point reflects where a decision takes place to engage a subsequent process scenario and/or to alter the existing process scenario. The information about activities taking place from a prior decision point is provided to the decision maker and reflects benefits and risks of changes to process scenario sequencing.

As described above, to make a decision, information that constitutes a cost-benefit justification of changes to the process scenario is calculated. The information is used to determine levels of information system automation and modularity that are required to increase information value and to decrease the cost of the activities or to drive more responsiveness to changing environmental conditions and/or influences that impact the enterprise and their processes.

Table 21 shows an exemplary definition of a value element object. Other embodiments may employ a different type of table with different fields.

TABLE 21 Field Object Reference Table Name Field Type Req Description Use Check Type Ref. Values ID General M A non-intelligent Used to Auto N value that defines uniquely number the unique “key” identify the for the database object as a record record and for relating it with other objects Name M A non-intelligent Used to Character, N standard value provide the Field that describes the primary entry, object means of Length = 30 identifying and searching Description M An intelligent, Used to Character, N non-standard provide a Field value that secondary entry, describes with means of Length = 255 detail identify and searching Category Classification M The field that Used to Character, Y Relevancy, identifies the key identify the Selection, Velocity, attribute drive the generation of Length = 15 Completeness, enterprise value value or how Accuracy value will be boosted Type M The field that Used to Character, Financial, determines the identify how Selection, Performance, nature of the the value is Length = 15 Quality, Image, value that will be used to Goodwill, result as of the improve the Standing, etc. improvement worth of the enterprise Enterprise Relationship M The field that Used to link OBJID Numeric, Y ID value from Objective contains the the two (foreign Selection, the Enterprise Object ID information object objects and key) Length = 7 Objectives identification key describe that Table relationship Enterprise M The field that Used to link OBJNAM Character, Y Name value Objective contains the the two (foreign Default, from Enterprise Object information object objects and key) Length = 30 Objectives Name name value describe that Table auto- relationship selected based on OBJID Enterprise M The field that Used to link BENID Numeric, Y ID value from Benefit contains the the two (foreign Selection, the Enterprise Object ID information object objects and key) Length = 7 Benefits Table identification key describe that relationship Enterprise M The field that Used to link BENNAM Character, Y Name value Benefit contains the the two (foreign Default, from Enterprise Object information object objects and key) Length = 30 Benefits Table Name name value describe that auto-selected relationship based on BENID Performance M The field that Used to link PERID Numeric, Y ID value from Metric contains the the two (foreign Selection, the Object ID information object objects and key) Length = 7 Performance identification key describe that Metrics Table relationship Performance M The field that Used to link PERNAM Character, Y Name value Metric contains the the two (foreign Default, from Object information object objects and key) Length = 30 Performance Name name value describe that Metrics Table relationship auto-selected based on PERID Lifecycle Lifecycle M The field that Used to Date, Y Julian Calendar; start date identifies when provide a Field Format = YYYY/ the value element window of entry, MM/DD would begin opportunity Length = 10 for the element Lifecycle M The field that Used to Date, Y Julian Calendar; end date identifies when provide a Field Format = YYYY/ the value element window of entry, MM/DD would end opportunity Length = 10 for the value element

Processes

These above-described objects may be used to define a business process, and to define how different business processes generate value for an enterprise based, e.g., on their domain assignment, contribution to business objectives, benefits produced for the enterprise, and the like. The objects also define business processes by specifying environmental settings in which a process operates, and influences that impact the process.

The EAAF stores objects that define individual processes or larger processes (referred to as “scenarios”) within an enterprise. These objects are built using the core objects and relationships objects defined above. They also exist in conjunction with the value objects, which define conditions in which those processes operate.

Cell

Objects may be mapped within an enterprise decision control domain using common and cross-object relationships and information regarding those relationships. A single set of core objects related by cross-object relationship objects constitutes a cell. Generally speaking, a cell includes a set of elements needed to complete an objective, and to derive information related to the objective, so that a decision can be made by a participant or so that information can be transformed to a state that is usable by another cell.

FIG. 5 shows a cell conceptually. As shown in FIG. 5, cell 49 is defined by core objects 50 to 52 and relationships 54 to 57 between those core objects. The relationships are defined by cross-object relationship objects, which are described above.

In this embodiment, cells are objects, which are defined by tables. An example of an object description table for a cell is shown below in Table 21. Other embodiments may employ a different type of table with different fields.

In Table 22, the basic relationships between the four core elements defined in the object, namely the participant object, the information object, the activity object and the enabler object, are defined by applying cross-object relationships to those core objects. In this example, the cross-object relationships, which are also defined in the cell object, include the participant to information object, the activity to information object, and the enabler to activity object. It is noted that cells may be time-dependent, meaning that they may be valid only for specified periods of time.

TABLE 22 Field Object Reference Table Field Name Type Req Description Use Check Type Ref. Values ID General M A non-intelligent Used to Auto N value that defines uniquely number the unique “key” identify the for the database object as a record record and for relating it with other objects Name M A non-intelligent Used to provide Character, N standard value the primary Field that describes the means of entry, object identifying and Length = 30 searching Description M An intelligent, Used to provide Character, N non-standard a secondary Field value that means of entry, describes the identify and Length = 255 object with detail searching Type Classification M The field Used to classify Character, Y Operation, indicates whether the cell Selection, Event, Trigger, the domain is Length = 25 etc associated with a standards organization Participant to Relationship M A non-intelligent Used to Number, Y ID value from Enabler ID value that defines uniquely Selection, Participant to the unique “key” identify the Length = 7 Enabler Cross - for the database object as a Object record record and for Relationship relating it with Table other objects Participant to M A non-intelligent Used to provide Character, N Name value Enabler standard value the primary Default, from Name that describes the means of Length = 30 Information object identifying and Table Auto- searching selected based on A2IID Activity to M A non-intelligent Used to Number, Y ID value from Information value that defines uniquely Selection, Activity to ID the unique “key” identify the Length = 7 Information for the database object as a Cross-Object record record and for Relationship relating it with Table other objects Activity to M A non-intelligent Used to provide Character, N Name value Information standard value the primary Default, from Name that describes the means of Length = 30 Information object identifying and Table Auto- searching selected based on A2IID Enabler to M A non-intelligent Used to Number, Y ID value from Activity ID value that defines uniquely Selection, Enabler to the unique “key” identify the Length = 7 Activity Cross- for the database object as a Object record record and for Relationship relating it with Table other objects Enabler to M A non-intelligent Used to provide Character, N Name value Activity standard value the primary Default, from Name that describes the means of Length = 30 Information object identifying and Table Auto- searching selected based on E2AID Currency Valuation O The field that Character, Y EUR, USD, defines the Selection, SKR, DKR, currency for the Length = 3 SFR, GBP, valuation SPA, etc Amount Valuation O The field that Currency, N Resource = (i)(f) defines the cost of Calculation, C + (t)(f)L + (v)(d) the cell's activity Length = 15 M = (o)(r)E; a cell type “event” or “trigger” has a cost = 0 Lifecycle Lifecycle M The field that Used to Date, Y Julian Calendar; start date identifies when determine the Field Format = YYYY/ the relationships time-period entry, MM/DD begin validity of the Length = 10 cell Lifecycle end M The field that Used to Date, Y Julian Calendar; date identifies when determine the Field Format = YYYY/ the relationships time-period entry, MM/DD end validity of the Length = 10 cell Decision Point Object

As noted above, to identify a process scenario's value within a given enterprise dimension and decision-control domain, a decision point is identified to determine where the valuation of the process scenario will occur. This point is where a decision, within the domain of a participants' authority, would take place to engage a subsequent process scenario and/or alter the existing process scenario. The decision point constitutes a point where an effective cost-benefit analysis can be executed for comparative analysis.

The above-noted cost-benefit analysis may be used to determine the level of information system automation and modularity that are required to facilitate increasing information value and decreasing cost of the activities or to drive more responsiveness to changing environmental conditions that are reflection of the degrees of freedom within an enterprise dimension. Thus, if more adaptation is required because of unpredictability from impacts to a process scenario caused by changing environmental conditions and influences, the need for flexibility and adaptation becomes greater. However, flexibility and adaptability should be weighed against the overall benefit derived from that particular process scenario, i.e., the output and benefit derived by the enterprise.

Table 23 shows an exemplary definition of an object that defines a decision point (e.g., a cell) within a process scenario for valuation purposes. Other embodiments may employ a different type of table with different fields.

TABLE 23 Field Object Reference Table Name Field Type Req Description Use Check Type Ref. Values ID General M A non-intelligent Used to Auto N value that defines uniquely number the unique “key” identify the for the database object as a record record and for relating it with other objects Name M A non-intelligent Used to provide Character, N standard value the primary Field that describes the means of entry, object identifying and Length = 30 searching Description M An intelligent, Used to provide Character, N non-standard a secondary Field value that means of entry, describes with identify and Length = 255 detail searching Category Classification M The field that Used to Character, Y Recurring, one- identifies the identify the Selection, time, cyclical, nature of the timing of the Length = 15 unique, etc. decision with decision and if respect to its it occurrence Type M The field that Used to Character, Time-based, identifies the identify how Selection, performance- basis or criteria the information Length = 25 based, financial- that drives the will be based, quality- decision point interpreted based, etc. within the process Information Relationship M The field that Used to link the INFID Numeric, Y ID value from Object ID contains the two objects and (foreign Selection, the Information information object describe that key) Length = 7 Table identification key relationship Information M The field that Used to link the INFNAM Character, Y Name value Object contains the two objects and (foreign Default, from Name information object describe that key) Length = 30 Information name value relationship Table auto- selected based on INFID Value M The field that Used to link the VALID Numeric, Y ID value from Element contains the value two objects and (foreign Selection, the Value Object ID element object describe that key) Length = 7 Element Table identification key relationship Value M The field that Used to link the VALNAM Character, Y Name value Element contains the value two objects and (foreign Default, from Value Object element object describe that key) Length = 30 Element Table Name name value relationship auto-selected based on VALID Lifecycle Lifecycle M The field that Used to provide Date, Y Julian Calendar; start date identifies when a window of Field Format = YYYY/ the decision point opportunity for entry, MM/DD would begin the decision Length = 10 point Lifecycle M The field that Used to provide Date, Y Julian Calendar; end date identifies when a window of Field Format = YYYY/ the decision point opportunity for entry, MM/DD would end the decision Length = 10 point Process Scenario

Cells may be linked together in a flow that reflects how information is transformed over time from one state to another state. This time-dependent flow is defined by each cell's information transformation requirements and how its influences impact existing environmental settings. A process scenario is a process that may be represented by linking multiple cells (or other types of “building blocks”).

FIG. 6 shows a conceptual view of a process scenario 60. As shown in FIG. 6, process scenario is made up of various cells 61, 62, etc. that are connected in a temporal string to define a process from start to finish.

Process scenarios are objects that are defined by object description tables. These tables define relationships that cells have to one another in the process scenario. Information objects in the cells of a process scenario link the various cells to form the process scenario. This configuration reflects the fact that a process (e.g., a cell) may be dependent on information from another process (e.g., a preceding cell). A common information object thus may link the two cells in a process scenario. Accordingly, a chain of cells, all of which are linked by their information objects, may form a process scenario. In other embodiments, objects other than the information object may link the cells.

Table 24 defines elements that are used to build process scenarios. Other embodiments may employ a different type of table with different fields.

TABLE 24 Field Object Reference Table Name Field Type Req Description Use Check Type Ref. Values ID General M A non-intelligent Used to Auto N value that defines uniquely number the unique “key” identify the for the database object as a record record and for relating it with other objects Name M A non-intelligent Used to provide Character, N standard value the primary Field that describes the means of entry, object identifying and Length = 30 searching Description M An intelligent, Used to provide Character, N non-standard a secondary Field value that means of entry, describes with identify and Length = 255 detail searching Domain ID Classification M A non-intelligent Used to Number, Y ID value from value that defines uniquely Selection, Decision- the unique “key” identify the Length = 7 Control Domain for the database object as a Table record record and for relating it with other objects Domain M A non-intelligent Used to provide Character, N Name value Name standard value the primary Default, from Decision- that describes the means of Length = 30 Control Domain object identifying and Table Auto- searching selected based on DOMID Lifecycle Lifecycle M The field that Used to provide Date, Y Julian Calendar; start date identifies when a window of Field Format = YYYY/ the scenario opportunity for entry, MM/DD would begin the scenario Length = 10 Lifecycle M The field that Used to provide Date, Y Julian Calendar; end date identifies when a window of Field Format = YYYY/ the scenario opportunity for entry, MM/DD would end the scenario Length = 10

Variations in influences and environmental settings that impact an enterprise dimension will impact each decision-control domain differently. This difference in the impacts creates the potential for conflicting optimization between decision-control domains. This is reflected through the structuring of process scenarios that optimize a single decision-control domain, but which, when linked with the other decision-control domains, can sub-optimize the entire enterprise.

Table 25 shows a table that defines a process scenario object. Other embodiments may employ a different type of table with different fields.

TABLE 25 Field Object Reference Table Name Field Type Req Description Use Check Type Ref. Values ID General M A non-intelligent Used to Auto N value that defines uniquely number the unique “key” identify the for the database object as a record record and for relating it with other objects Name M A non-intelligent Used to Character, N standard value provide the Field that describes the primary entry, object means of Length = 30 identifying and searching Description M An intelligent, Used to Character, N non-standard provide a Field value that secondary entry, describes with means of Length = 255 detail identify and searching Scenario Relationship M The field that Used to link SCNID Numeric, Y ID value from Object ID contains the cell the two (foreign Selection, the Scenario object objects and key) Length = 7 Table identification key describe that relationship Scenario M The field that Used to link SCNNAM Character, Y Name value Object contains the cell the two (foreign Default, from Scenario Name object name value objects and key) Length = 30 Table auto- describe that selected based relationship on SCNID Cell Object M The field that Used to link CELID Numeric, Y ID value from ID contains the cell the two (foreign Selection, the Cell Table object objects and key) Length = 7 identification key describe that relationship Cell Object M The field that Used to link CELNAM Character, Y Name value Name contains the cell the two (foreign Default, from Cell Table object name value objects and key) Length = 30 auto-selected describe that based on CELID relationship Influence O The field that Used to link IFLID Numeric, Y ID value from Object ID contains the the two (foreign Selection, the Influence influence object objects and key) Length = 7 Table identification key describe that relationship Influence O The field that Used to link IFLNAM Character, Y Name value Object contains the the two (foreign Default, from Influences Name influence object objects and key) Length = 30 Table auto- name value describe that selected based relationship on IFLID Environmental M The field that Used to link ENVID Numeric, Y ID value from Setting contains the the two (foreign Selection, the Object ID environmental objects and key) Length = 7 Environmental setting object describe that Settings Table identification key relationship Environmental Relationship M The field that Used to link ENVNAM Character, Y Name value Setting contains the the two (foreign Default, from Object environmental objects and key) Length = 30 Environmental Name setting object describe that Settings Table name value relationship auto-selected based on ENVID Decision O The field that Used to link DPTID Numeric, Y ID value from Point contains the the two (foreign Selection, the Decision Object ID decision point objects and key) Length = 7 Point Table object describe that identification key relationship Decision O The field that Used to link DPTNAM Character, Y Name value Point contains the the two (foreign Default, from Decision Object decision point objects and key) Length = 30 Table auto- Name name value describe that selected based relationship on DPTID Relative Event M The field that Used to Numeric, Y 1, 10, 100, Time Sequence identifies the time determine the Selection, 1000, 10000, etc Increment increment for the increment of Length = 10 event sequence the relative time sequence Relative M The field that Used to Character, Y Milli-seconds, Time Scale identifies the time determine the Selection, seconds, scale for the event scale at Length = 20 minutes, hours, sequence which the days, weeks, relative time months, years, sequence etc. applies Relative M The field that Used to Numeric, N Format = 99999 Initial identifies the determine Field Time process scenario sequence of Entry, object's relative the process Length = 5 initial time scenario object in the event model Relative M The field that Used to Numeric, N Format = 99999 Final Time identifies the determine Field process scenario sequence of Entry, object's relative the process Length = 5 final time scenario object in the event model Information Valuation O The field Used to E2EPRO Numeric, N <velocity Velocity Metrics identifies the determine the Formula, {info object}> speed of the impact of the Length = 20 (time|final| − |initial|)/ information object enabler to [PSCRFT– time ID identified enabler PSCRIT] |standard| within the cell integration through a process with respect scenario to the call protocol Information O The field Used to P2ICRI Numeric, N <completeness Completeness identifies the ratio determined Formula, {info object}> of completeness the Length = 20 (# of data of the information participant's [manually elements object as managed use of the entered |entered| − |blank|)/ by the enabler enabler with values] # of respect to the data elements criticality |total| Information O The field Used to A2IINI; Numeric, N <accuracy {info Accuracy identifies the ratio check the A2IFIN Formula, object}>(# of the differences information Length = 20 physical object between the state before [manually attributes|state physical and and after entered x| − # of info information processing in values] object attributes characteristics relationship |state x|)/# of with respect to the to the state of physical object final number of the material attributes|final physical object or physical state| characteristic object Information O The field Used to E2IINI; Numeric, N <relevancy{info Relevancy identifies the ratio check at any E2IFIN Formula, object}>(information of the information point in time Length = 20 object to physical object the latency of [manually attributes|state characteristics at the entered x|)/physical any point in time information values] object attributes processing |state x| Activity The field Used to Numeric, N <capital cost Cost of identifies the cash determine the Formula, {activity Capital used/employed benefit Length = 20 object}> (cash for the activity [manually position|initial| − and the associated entered |final|) × cost of capital values] periodic rate |standard| Activity Valuation O The field Used to P2A Numeric, N <labor cost Cost of Metrics identifies the cost validate the Formula, {activity Labor labor associated level of Length = 20 object}> with the activity manual effort [manually (process time to perform an entered |final| − |initial|) × unit activity and values] labor cost the |periodic rate| × associated productivity level labor costs Activity O The field Used to Numeric, N <material cost Cost of identifies the cost validate the Formula, {activity Materials of materials usage of Length = 20 object}> (# of consumed for this materials [manually material activity including any entered components scrap for an values] |final| − |initial|) × unit activity material cost|standard rate|/scrap rate Activity O The field Used to Numeric, N <equipment cost Cost of identifies the cost validate the Formula, {activity Equipment of equipment utilization Length = 20 object}> utilized at a and cost of [manually (equipment standard rate equipment entered usage|time qualified by the rationalized values] final| − |time operating rate of by the initial|) × equipment the equipment operating cost rate of the |standard rate| × equipment operating rate) Valuating Information

The EAAF database makes it possible to valuate information that is transformed during a process scenario. To identify value in process scenario, a point (e.g., a cell) in the process scenario is selected. This point reflects where a decision would take place to engage a subsequent process scenario and/or to alter the existing process scenario. This decision point thus constitutes a point where a cost-benefit analysis can be determined. Such an analysis may be used to determine levels of information system automation and modularity that are required to increase information value and to decrease the cost of the activities or to drive more responsiveness to changing environmental conditions. For example, if more adaptation is required because of unpredictability from impacts to the process caused by changing environmental conditions and influences, the need for flexibility and adaptation becomes greater. However, flexibility and adaptability is weighed against the overall benefit derived from that particular process i.e., the output and benefit derived by the enterprise.

Since not all domains treat information consistently in terms of the impact or value of the decision made or activity undertaken, information has different valuations. The total value generated from a process scenario is directly proportional to the scope of impact either from a decision made by a participant or an activity executed, i.e., the value of impact, and is inversely proportional to the cost of the activities that are generating or transforming the information i.e., the value of activity. This can be expressed as a formula: Vt=Vi/Va, where Vt is the total value, Vi is the value of impact, and Va is the value of activity. These values are set forth in Table 25 above. The values of Vi and Va may be determined from elements of the various objects and other related information. In one embodiment, the value of Vi is determined using the following parameters, where the parenthetical indicates the object in the cell (at the decision point) from which the components used to derive the parameters are determined. For example, for the “velocity” parameter, the components, e.g., “time|final|” are obtained from the information (“info”) object. The probability factor, which does not contain a parenthetical, is input by an administrator based on knowledge of the process scenario. velocity{info object}=(time|final|−time|initial|)/time|standard|) completeness{info object}=(data elements|entered|−data element|blank|/data elements|total|) relevancy{info object}=(information object attributes|state x|/physical object attributes|state x)| accuracy{info object}=(# physical object attributes|state x|−# of info object attributes|state x|)/# of physical object attributes|final state|) cash flow{info object}=(cash generated|revenue or cost attributed to information object|] probability factor=achieving the correct and timely decision from information object obtained by a user

The value for Vi is determined as follows: Vi=(velocity+completeness+relevancy)×(accuracy)×(cash flow)×(probability factor) In one embodiment, the value of Va is determined using the following parameters capital cost{process object}=(cash position|final|−cash position|initial|)×interest rate|standard rate|×differential|rate| labor cost{process object}=(process time|final|−process time|initial|)×unit labor cost|standard rate|×productivity level material cost{process object}=(# of material components|final|−# of material components|initial|)×unit material cost|standard|×percent scrap equipment cost{process object}=(equipment usage|time f|−equipment usage|time i|)×unit equipment cost|standard rate|×operating rate probability factor=accuracy of the data values for the process object

The value for Va is determined as follows: Va=(capital cost+labor cost+material cost+equipment cost)×(probability factor)

Once Vi and Va are determined, Vt can be determined. It is then possible to alter conditions in the process scenario to affect the value of Vt, i.e., to increase or decrease Vt. This increase or decrease corresponds to the effect on the value generated by the process scenario at the decision point.

Enterprise Scenario

Different decision control domains (i.e., layers) may be “stacked” in a single EAAF database. The different layers may be integrated to model an enterprise. In one embodiment, these layers include a strategic layer, an operational layer, and a tactical layer.

In general, the strategic layer contains cells that drive and measure a business, including products, customers, resources, etc. The strategic layer deals with questions relating to how a company does business to make money and what business elements contribute to the creation of value for the enterprise and for their customers (as viewed by shareholders, stakeholders and customers alike).

Objects in this layer may include, but are not limited to the following. Information objects include business objects that directly touch physical objects, i.e., products, customers, suppliers, labor as well as their support objects, contracts, designs, and the like. Participant objects define information owners who are responsible for timely decisions and outcomes. Enabler objects include types of applications and tools on which data equivalents of the information objects reside, such as business intelligence tools and data warehousing applications. Activity objects relate to enterprise and product value-chain activity elements constructed and sequenced for enterprise level optimization of deliverables and performance results.

The operational layer contains cells that define information states and object clusters related to activity sequences (e.g., input/output). The operation layer deals with questions relating to how the company delivers products and operates as an enterprise.

Objects in this layer may include, but are not limited to the following. Information objects include business object components, i.e., materials, credit rating, payment term, work schedules, etc., and related support objects, agreements, drawings, etc. Participant objects include process scenario owners responsible for operational performance. Enabler objects include applications where processes reside that transform data objects when triggered by events and constraints based on data object sharing. Activity objects include business operations and support activity elements constructed and sequenced for operational level optimization of deliverables and performance results.

The tactical layer contains cells, comprised of core objects, that define information states and object clusters related to activity sequences (e.g., input/output). The operation layer deals with questions relating to how the company transacts, i.e., different task-flows that enable the company to operate efficiently in different environments through automation of its technical and business transactions.

Objects in this layer may include, but are not limited to the following. Information objects include objects identifying attributes, states, predictability, and reliability at each execution stage of an activity with contextual references for comparability. Participant objects define participants responsible for transaction input, output, usage, support and performance. Enabler objects define tool and application interoperability and role-based access to ensure that specific process scenarios can be executed and performance targets specified. Activity objects define procedures and activity elements constructed and sequenced for tactical level optimization of deliverables and performance results.

FIG. 7 shows an example of process scenarios for different layers of an enterprise. More specifically, as shown in FIG. 7, strategic layer 64 includes two process scenarios 65 and 66 for its “pulp production” element 67 a. In operational layer 67, “pulp production” element 67 a includes process scenario 69 to implement a “mechanical grinding” step 70. In tactical layer 71, two process scenarios 72 and 73 are implemented in the step 74 for determining a wood type to use for pulp production.

EXAMPLE

The following example illustrates the how to use the EAAF database in an analysis. This example begins by defining process scenario objects that utilize relationships of a decision point, influences and environmental settings to the process scenario, and cells that facilitate dynamic re-sequencing of event chains. i.e., process scenario objects

This example relates to a fictional company that has a manufacturing operations in China and in the southeastern United States, and compares operational performance and process adaptability. To analyze the company, the following are determined, which have an impact on how effectively an event sequence, i.e., the process scenario, can be adapted to a new conditions: environmental settings, influences, and a decision point.

In this example, the company has two plants—one located in the southeastern United States and the other located one in the Shandong Province near the city Weihai, China. Both plants produce the same goods. The U.S. plant produces the goods for the American and European markets and the Chinese plant produces the goods for the Middle-East and Asian markets. Given the need for the consistency in quality due to the global nature of their customers, identical production processes are deployed in both plants. The equipment and factory floor layout is identical to optimize asset investments and reduce unique training and maintenance expenses. Both plants use the same global raw material vendor to ensure consistent quality control. The employees attend similar training classes and their job roles are substantially identical in nature.

In this example, the company receives a large order, which exceeds its normal operating capacity given set-up and maintenance time required during a production run. The company needs to evaluate their flexibility to determine how they can optimally produce goods for the order without wholesale outsourcing, which reduces the overall profitability of the order. Given that most of environmental settings that would impact the production are consistent, e.g., knowledge and skill (productivity), material quality (scrap rates), machine capacity (production capacity), it would appear that there are no differences is the degrees of freedom, i.e., the variability of the sequence of events within the process scenario, that would provide information to the company's decision makers regarding optimization of the company's production facilities.

Factors that may have been initially overlooked, or that may not be typically included in enterprise architectural system modeling tools, include the relationship of environmental factors relating to culture and to political influence to the process scenario (i.e., the event sequence that occurs in the plant to satisfy the order). This is due to the fact that these factors may not impact or relate at the tactical layer of the decision control domain. Nor would these factors impact information requirements for supporting the production process, maintenance processes, and quality processes that are needed to manage optimization of the company's manufacturing process. The tactical layer considers various factors that would impact the manufacturing processes, such as those noted above. Thus, an enterprise architecture system that evaluates the information requirements to support that level would only consider those factors

At the operational decision-control domain, the cultural and political factors do have an impact on information and, in turn, decisions made from that information. The linkage of these factors to the process scenario provides an opportunity to re-sequence the process scenario to optimize events. To do so requires several linkages between objects, and not a simple relationship of environmental and influence factors to a process scenario. First, since impact and evaluation occurs on a higher domain level, and the decision point is linked to information, an information to information relationship is used to establish a structure of the information necessary to make the decision. Latency of the information object that is reported or used for a decision is considered, since making the decision requires that the information state be known, so as to determine its relevancy to an actual state of the physical world. For example, production work-in-process must be known and the identities of information systems reporting the work-in-process must be known, along with whether the work-in-process is batch or real-time. This information is used to determine the -in-process latency in a report. This will provide decision makers with the current excess capacity that may be available at the time of the decision.

The decision-point in the process scenario object is determined beforehand, making it possible to correctly determine a place in the event sequence where the information is reported, and whether the remainder of the event or subsequent events can (or cannot) be re-sequenced. Without this knowledge, it may be possible to execute one or more process changes, but the process may be too advanced to permit a wholesale change of the events. In this regard, the fact that there is a cellular structure to the event sequence does not imply that cells that comprise a process scenario can be dynamically re-sequenced at any point. The decision-points are the control points at which changes can be introduced into the event sequence so as not to sub-optimize the lower or higher domain levels.

Finally, the valuation metrics are associated with the process scenario object at the decision point within the event sequence. This is the case in order to drive the cost benefit associated with reconfiguration of the event (process scenario) sequence. The valuation of the information includes the accuracy, completeness, relevancy and velocity of the information and the value of the activity includes the cost of capital, labor, resources and materials necessary for the event chain that is comprised of the process scenario objects between the decision-control points in an event chain. Thus, this contiguous set of cells produces a value metric that is measurable and useful in evaluating opportunities, such as options for increasing production capacity as is in this example.

With the defined relationships mentioned above, and the relationship of environmental and influence factors to the process scenario object, the operational level management can evaluate the options available to them and the impact of any decision. Thus, in this example, the social influence on the US manufacturing operations was positive in the sense that the company wants to expand their production facility in their area to promote higher paying manufacturing jobs. Thus, the company could impose weekend overtime without a lose of employee productivity and morale.

The environmental setting in Chinese province discourage companies from imposing work rules that impede quality of family life, combined with regulation influence that would require additional production reporting for the addition work time. This has a negative impact on re-sequencing the event chain to allow for higher production output through double shifts or changes in the production rates. These induced changes would cause worker productivity to decrease and increase overall production costs.

Generating Reports

As described herein, the EAAF database acts as a “storage area” for elements of an enterprise architecture. By querying the EAAF database, it is possible to generate reports relating to an enterprise. For example, two categories of reports may be generated: one that give an overview of an existing information system (IS)/information technology (IT) landscape, and one that identifies gaps in, and impacts of, a new IT solution.

Examples of reports that may be generated include (a) A list of values (name, descriptions, etc.) linked to a scenario for a layer number. The reports list a date of a window of opportunity relating to realization of a value and an expected amount. (b) A list of all basic cells of a scenario. The report lists participants (record id, name), activities (record id, name), information (record id, name) and enablers (record id, name). (c) For a given scenario, a list of all participants of cells in the scenario or in scenarios in the given scenario. (d) For a given scenario, a list of all information for cells in the scenario or in scenarios in the given scenario. (e) For a given scenario, a list of all enablers of cells in the scenario or in scenarios in the given scenario. (f) For a given scenario, a list of all activities of cells in the scenario or in scenarios in the given scenario. (g) A list of all tables sorted by any fields of the table. Other reports also may be generated. Likewise, the EAAF may be queried for any information that it contains.

Hardware and Software

The EAAF database may be built on, and used in conjunction with, any hardware and software. The EAAF database may find applicability in any computing or processing environment and with any type of machine that is capable of running machine-readable instructions, such as a computer program. The EAAF database may be implemented in hardware, software, or a combination of the two. The EAAF database may be used in conjunction with computer programs executing on programmable computers that each include a processor, a storage medium readable by the processor (including volatile and non-volatile memory and/or storage elements), at least one input device, and one or more output devices. Program code may be applied to data entered using an input device (e.g., a mouse or keyboard) to build and/or access the EAAF database.

Each such program may be implemented in a high level procedural or object-oriented programming language to communicate with a computer system. However, the programs can be implemented in assembly or machine language. The language may be a compiled or an interpreted language.

Each computer program may be stored on a storage medium or device (e.g., CD-ROM, hard disk, or magnetic diskette) that is readable by a general or special purpose programmable computer for configuring and operating the computer when the storage medium or device is read by the computer to build and/or access the EAAF database. The EAAF database may also be implemented on one or more computer-readable storage media, configured with or without a computer program.

The EAAF database is not limited to the embodiments set forth herein. Other embodiments are also within the scope of the following claims. 

1. A method of modeling an enterprise, comprising: performing the following actions on a processing device: defining core objects, the core objects comprising information objects defining information used in the enterprise, participant objects defining participants in the enterprise, enabler objects defining tools used in the enterprise, and activity objects defining processes performed in the enterprise; defining relationship objects that define interactions between two or more of the core objects; defining cells comprising at least an information object, other core objects, and relationship objects, each cell being an object for linking sets of core and relationship objects needed to complete a specific objective and/or derive information; defining a process scenario object in which two or more cells are linked, the process scenario object defining how information is transformed over time among cells; defining a domain that relates the process scenario object to one or more other domains hierarchically via one or more other process scenario objects; and generating a report that is based on the modeling of the enterprise; wherein the process scenario object comprises references to value objects that have an affect on a corresponding process scenario, the value objects defining: environmental conditions that drive the process scenario, external influences on the process scenario, and objectives of the enterprise; wherein the process scenario object comprises a reference to a decision point object, the decision point object specifying a point, in the process scenario, where a change can be made without adversely affecting the one or more other domains, the decision point object specifying a value analysis to be performed at the point specified in the decision point object, the value analysis for determining whether to alter the process scenario or to engage a subsequent process scenario, information corresponding to the value analysis being associated with the process scenario object; wherein the process scenario object defines a chain of cells, each cell in the chain of cells being linked to at least one of an immediately preceding cell or an immediately succeeding cell via an information object that is common to the cell and the immediately preceding cell or the immediately succeeding cell; and wherein the value analysis comprises a cost/benefit analysis relating to whether to alter the process scenario or to engage a subsequent process scenario, the cost/benefit analysis for weighing a benefit of the process scenario against a benefit related to an alteration of the process scenario or engagement of a subsequent process scenario.
 2. The method of claim 1, wherein each domain comprises a decision-making layer within the enterprise.
 3. The method of claim 1, wherein an information object is common to the process scenario object and a second process scenario object.
 4. The method of claim 1, further comprising: performing the following action on a processing device: storing, in a value element object linked to the process scenario object, a value of information transformed via the process scenario, the value of the information corresponding to a result of the cost/benefit analysis.
 5. The method of claim 1, wherein the relationship objects define one of common object relationships and cross-object relationships.
 6. The method of claim 1, wherein the value objects further comprise at least one object to define a benefit of the enterprise, and at least one object to define a performance metric associated with the enterprise.
 7. The method of claim 6, wherein the performance metric comprises at least one of an industry metric and a government metric.
 8. One or more machine-readable media for storing instructions for modeling an enterprise, the instructions being executable to: define core objects, the core objects comprising information objects defining information used in the enterprise, participant objects defining participants in the enterprise, enabler objects defining tools used in the enterprise, and activity objects defining processes performed in the enterprise; define relationship objects that define interactions between two or more of the core objects; define cells comprising at least an information object, other core objects, and relationship objects, each cell being an object for linking sets of core and relationship objects needed to complete a specific objective and/or derive information; define a process scenario object in which two or more cells are linked, the process scenario object defining how information is transformed over time among cells; define a domain that relates the process scenario object to one or more other domains hierarchically via one or more other process scenario objects; and generate a report that is based on the modeling of the enterprise; wherein the process scenario object comprises references to value objects that have an affect on a corresponding process scenario, the value objects defining: environmental conditions that drive the process scenario, external influences on the process scenario, and objectives of the enterprise; wherein the process scenario object comprises a reference to a decision point object, the decision point object specifying a point, in the process scenario, where a change can be made without adversely affecting the one or more other domains, the decision point object specifying a value analysis to be performed at the point specified in the decision point object, the value analysis for determining whether to alter the process scenario or to engage a subsequent process scenario, information corresponding to the value analysis being associated with the process scenario object; wherein the process scenario object defines a chain of cells, each cell in the chain of cells being linked to at least one of an immediately preceding cell or an immediately succeeding cell via an information object that is common to the cell and the immediately preceding cell or the immediately succeeding cell; and wherein the value analysis comprises a cost/benefit analysis relating to whether to alter the process scenario or to engage a subsequent process scenario, the cost/benefit analysis for weighing a benefit of the process scenario against a benefit related to an alteration of the process scenario or engagement of a subsequent process scenario.
 9. The one or more machine-readable media of claim 8, wherein each domain comprises a decision-making layer within the enterprise.
 10. The one or more machine-readable media of claim 8, wherein an information object is common to the process scenario object and a second process scenario object.
 11. The one or more machine-readable media of claim 8, further comprising instructions to: store, in a value element object linked to the process scenario object, a value of information transformed via the process scenario, the value of the information corresponding to a result of the cost/benefit analysis.
 12. The one or more machine-readable media of claim 8, wherein the relationship objects define one of common object relationships and cross-object relationships.
 13. The one or more machine-readable media of claim 8, wherein the value objects further comprise at least one object to define a benefit of the enterprise, and at least one object to define a performance metric associated with the enterprise.
 14. The one or more machine-readable media of claim 13, wherein the performance metric comprises at least one of an industry metric and a government metric. 